I've heard people say they have gotten Odin to work on their 64 bit versions of windows, but I cant. I am able to use it on a computer running Windows 7 - 32bit, but not either of the computers I've got running 64 bit.
I've definitely installed the 64 bit the drivers. I can access the phone in ADB on these computers. Odin sees the phone and throws up a com port, but I get a weird error message with Chinese characters when I try to move forward with the flash.
Anyone have a definitive answer? Is it possible to use Odin on Win 7 64bit?
I flashed the leaked J12 with Odin on my 64bit Windows 7 laptop without any trouble.
I flashed with Odin on my W7 64bit desktop. Had a little trouble with it sticking on the verifying files at the beginning, but restarted it and it ran fine the second time. That's the only experience I've had with Odin. Just though I'd let you know that it works on my 64bit machine.
Thanks guys. I dont know what the hiccup is on my end. I might go through my drivers again just to make sure that isnt the issue.
I would highly suspect that the drivers are the issue as have used Odin on 2 separate 64bit machines. Make Sue that after u download the Sammy drivers, that they are installed, and installed correctly.
they call me...kick ass
I was never able to make any win7 system recognize my vibrant in dl mode at all, 32 or 64 bit, no matter what drivers i tried. I even tried to extract the 64 bit drivers to the 32 bit Os as I had seen mentioned in a thread some people had success with. Xp ran it like a champ on the first attempt.
Sent from my SGH-T959 + bionix 1.3 (= sexiness) using XDA App
I know were talking about different phones here but I've been scouring the internet trying to find a solution to a problem I'm having right now. when switching from 1 custom ROM to another, it was required that I flash to stock EC05, then flash to EE?? my Windows 7 Ultimate x64 wouldnt work properly (kept getting stuck in boot.bin in ODIN0 but my old faithful Netbook with Windows XP Home SP3 (x86) workd flawlessly!
I'm talking 3 HOURS of trying to get the Win7x64 to work properly and had my Epic reflashed with XP in 3minutes and 27 seconds, not counting time to install Samsung Drivers into XP (30-45 seconds)
Granted this is my experiance, but before I got x64 I was running with Win7 X86 and still never had problems. I have read through Google search that other people with x64 Windows 7 had problems. This is my story only, best of luck to ya, but I am now ONLY going to use my ol Netbook (or x86 virsion of Windows) to ODIN my phone.
Never Stop Wanting More from your devices.
Im using 64 windows OS and i don't have a problem. If your device is not recognize by your PC just reinstall the samsung drivers and you are good to go.
Sometimes you have to go into the safe mode options and disable driver enforcement policy. Then it will work.
Sent from my SGH-T959 using xda premium
Related
I recall reading that the software for unlocking/flashing custom roms was for XP only. Is there a solid, working solution for Vista yet? If not, is anyone planning to make one?
How does activesynch work with vista & outlook 2k7? Any downsides to upgrading?
Might have been problems with Vista 64, I'm running Vista 32 and have never had a problem with custom roms.
Im a vista user and never had any problems, i never read too much into it but from what i understand its because they dont update their drivers. Someone posted the driver update in this section. Ive tried dcd's and currently using no2chems latest.
Using Vista
I use Vista on my laptop and have been experimenting with the HTC Titan since mid December.
So far, I never had an issue with Vista ( and I have experimented lots!!)
The only thing with Vista on my phone compared to my XP desktop at work is that the transfer of files to the HTC is must faster with XP. The XP machine also connects and syncs a bit faster than the Vista.
I can confirm that running Titan_Unlocker, and loading ROMs via Vista 32 with Windows Mobile Device Center works just fine.
Vista USB
I have not been able to connect with USB on my computer runing vista. I use of course windows mobile device and connect thru bluetooth, but have never been able to connect with usb. I checked the setting I WMB and have allow usb connection,.
I can tell you from experience that flashing thru bluetooth boes not work. Tried it about a year age with the Vzw upgrade on my 6700, locked up in bootloader screen, I took it to vzw and they gave me a new 6700.
That's odd ^
My Sync works both ways, and out does XP in every single way.
Vista performance depends on hardware mostly, and top notch gets you top performance.
I haven't had any problems syncing with vista.
I did have one problem when trying to upgrade to a custom rom and maybe someone here can help me answer it.
I got the sprint 3.16 test rom on there ok, then i installed the unlocker, but i couldn't get out of bootloader screen. I had the exit bootloader program but it kept saying it couldn't find the usb. then i tried attaching it to my xp comp and running the exit bootloader app and it said it was missing some dll file. so i tried redownloading and even emailing the exit bootloader from my other comp but same issue, missing dll file.
I ended up just loading the relocker and then going straight back to the latest rom because i couldn't figure it out.
I used the QDLtool to unstick my Streak so I am now on a pre release of 2.2. I am trying to upgrade to Steve's 1.5.3 but cannot even get the blasted streakmod recovery to flash as it keeps saying "waiting for device" on the cmd window but my Streak is in Fastboot_Mode. If I was able to fix my phone via QDL a few days ago then the drivers are all installed correct, right? I am running a 64 bit of Windows 7.
This is starting to overwhelm me...
I have played with W7 and drivers before. Other people have used W7, but it can be fiddly. If its possible, do yourself a favour and use XP.
Sounds like you still have drivers to install. I know I had to run an installation .exe file before the proper drivers were installed (XP).
Sent from my Dell Streak using XDA App
thestreaker said:
I have played with W7 and drivers before. Other people have used W7, but it can be fiddly. If its possible, do yourself a favour and use XP.
Sounds like you still have drivers to install. I know I had to run an installation .exe file before the proper drivers were installed (XP).
Sent from my Dell Streak using XDA App
Click to expand...
Click to collapse
Unfortunately, the only other pc in our house runs Vista. The computer I had before this one had XP but it had bad capacitors and fried the mobo.
I can't understand why I would need more drivers if I was able to use the QDLtool a few days ago with no problems on this same laptop. Who knows... they have minds of their own it seems.
Hopefully I can get it figured out bc its driving me insane!
Have you tried the solution in this guide:
http://forum.xda-developers.com/showthread.php?t=776883
I have to go through this method everytime I go into fast mode
Sometimes it feels like I have to bring an altar and a live chicken out just to get the drivers working
I use win 7 64
So, quick backstory. I have two PC's at home. A brand new win 7 64 bit laptop, and an older XP desktop. Neither will recognize my vibrant, and never have. At work, I have a win XP desktop, and I can connect the phone to that and use mass USB storage and move stuff around just fine, so I've gotten by in that regard in these 6 long months.
Then comes this #$%%^$#$ Froyo update. Who thought it would be easy?
I have downloaded kies on each machine. (As well as ODIN, but same issues.....computer/phone wont communicate). I cannot get my two home computers to connect to the phone, no matter what settings. BTW, I have rooted my phone with OCLF and subsequently un-rooted before trying any of the following. I have not flashed or updated the phone otherwise with any other software, other than what apps are available in the market.
I've tried
-USB Debugging on/off
-all 10 USB ports between the three PC's in all configurations
-deleted all USB drivers and restarted on both computers
-installed the appropriate drivers from samsung for each pc
-wasted 7 hours with samsung support troubleshooting to no avail
The USB cable is fine. The most promising progress is on my work PC, where I got Mini Kies going, connected and started the update, it finished decompressing the binary files, but then a USB not recognized warning pop up and kies kicked out the update.
I have installed, reinstalled the drivers for each system several times with samsung support. Nothing is working.
I don't know what else to do. This is the most frustrating experience in my life. Any suggestions or similar experiences that have been remedied?
I was having promblems also but eventually got it to work for me on an xp machine on stock jfd. It updated me to ji6 then I did the ka6 update when it was released. I gave up on my win7 system lol. Is your xp system 32bit or 64?
Sent from my SGH-T959 using XDA App
same here i have a win7 64 bit machine, i can connect to normal kies 1.51. i tried to update, it downloaded the files and just got stuck when it started putting it on the phone (luckily, it did not start the installation so i was okay).
mini kies shows that it recognizes my phone but crashes immediately after that.
i do not think the vibrant is supported by newer versions of kies, like 2.0.
I solved my problem by using my 32bit xp system.
edit: just FYI, i can connect to normal kies 1.51, sync my data and all that stuff. i also updated to ji6 thru normal kies, and I can transfer files and whatnot thru usb. I do not even think i needed to install the drivers manually
I downloaded Mini Kies 2.0 onto my windows 7 64bit machine and installed the Samsung drivers I have everything worked smoothly. I upgraded 3 phones to Froyo with no issues. here are the drivers I have
http://71.228.63.153/download/usb_drivers_GalaxyS_x64.zip
toeshot said:
I downloaded Mini Kies 2.0 onto my windows 7 64bit machine and installed the Samsung drivers I have everything worked smoothly. I upgraded 3 phones to Froyo with no issues. here are the drivers I have
http://71.228.63.153/download/usb_drivers_GalaxyS_x64.zip
Click to expand...
Click to collapse
I did the Same thing it worked for me as well
The only luck I've had is on a winXP 32 bit machine, but then it cuts off the installation when it suddenly says "USB Not Recognized" (despite, um, the fact that it recognized it at the beginning, otherwise I wouldn't have been able to initiate the update!)
I'll give those Win7 64 drivers a try at home, although I'm pretty sure I have downloaded the same ones in my quest for a solution.
Do you suggest plugging in the phone, then installing the drivers, or leaving the phone unconnected and restarting the computer then trying to connect, or ???? The biggest issue on the Win7 machine is the phone not communicating with it AT ALL. Not even showing up in device manager as unknown or anything.
Moved of: Samsung Vibrant > Vibrant General
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
SOLVED
I finally got it to work, after about 15 attempts! (on a win XP machine)
Here's what I did in case it will help someone else:
When I plugged in my phone, I saw two items in the USB list in device manager. One said "Samsung Android USB Composite Device" (internal SD?), and the other said "USB Mass Storage Device" (external SD?). In this configuration, I got kicked out of the install each time after it "decompressed the binary files".
So what I did on a hunch was go to the device manager and "update" the driver for the USB Mass storage device to the "ssadadb2.inf" file included in the Vibrant USB drivers available directly from Samsung's Vibrant page.
Selected "Samsung Kies" on the USB settings on the phone, turned on USB Debugging, opened Kies on the computer, plugged in the phone, and it did it's thing.
Only took 3 days to figure it out!
Yeah its been a hit or miss. I have win7 x64 on two laptops and my desktop. It works in the desktop and only one of the laptop and I installed the same drivers for all 3
Sent from my SGH-T959 using XDA App
toeshot said:
I downloaded Mini Kies 2.0 onto my windows 7 64bit machine and installed the Samsung drivers I have everything worked smoothly. I upgraded 3 phones to Froyo with no issues. here are the drivers I have
yeah it works for me too, i just installed these drivers and put usb debugging mode. upgrading just now. thanx
Click to expand...
Click to collapse
W/ WIN 7 64 Bit I upgraded my phone to Froyo.
I'm running win 7 SP1 64 bit.
Samsung told me that Kies mini and the driver is not compatible to 64 bit.
After some research this is what I have done and able to upgrad my phone to Froyo.
1. check the USB debugging.
- Samsung says to uncheck it. but if you do, you probably have MTP USB device error. So make sure your USB debugging is on.
2. After the you connect your phone, Samsung Kies Mini keeps crashing??
-Uninstall IE 9.
Solution is...
*Check the USB Debugging and Uninstall IE 9.
**Make your the battery is fully charged.
Connect phone
Start Kies Mini
I got so sick of Windows I switched to Ubuntu Linux. It's free and just as easy to use as windows. No crashes, no viruses, and it sets up as a dual boot so I can use windows when necessary.
Nowadays, I use my Asus Netbook with WinXP to run RSD. But my girlfriend stole my netbook and now, I only have my macbook pro and I don't want to run Windows with boot camp.
So, the question is: Any of you already tried to use parallels with Win7 64 bits to flash SBF files and do all the other stuffs? I know we must not do some tasks on a virtualized environment, but RSD is running OK and I would like to hear your opinions about this.
I found on other threads people saying that there is no problem flashing roms using parallels, but we are on a motorola environment.
I just want to make sure that I'm not going to brick my phone because of this.
thanks.
I have used RSD using Windows XP & parallels no problem.
I've always paid close attention to the prompts for where to connect the new USB device and have never had any problems. I have done the SBF to unlock the bootloader as well as flash to 1.8.3.
I use moto-fastboot-osx32 for all my fastboot needs.
My version of Parallels is: 6.0.12090 Revision 660720, Windows XP 32 bit SP3 SP3, RSD Lite 5.3.1
Host is a Macbook Pro 6,1 i7 2.6ghz, OSX 10.6.8 (10.6.7 also)
I've always been running on battery when I flashed not that it should make a difference.
Presumably, Windows 7 should function as well.
Hope this is helpful.
I am currently running OS X Snow Leopard 10.6.8 on a Macbook Pro
I use VirtualBox (free, www.virtualbox.org) and I run Windows XP in a virtual environment on my Mac
I can do EVERYTHING you would ever need to do regarding the Atrix -> RSD, fastboot, adb, androidSDK, run scripts from command prompt to apply mods (such as the wake on volume keys and webtopmodhack install.bat files)
Nice to hear that. Don't want to brick my phone because of a stupid thing. It is always good to ask. Thanks for replying.
goTouch said:
my girlfriend stole my netbook
Click to expand...
Click to collapse
Sure she is the girlfriend and not you? LOL
Go get it back playa!
I haven't had any issues using Parallels 7 w/ Lion / Win7. We're working on Android and iOS though. Not sure about Motorola but I suspect it will work. Good to be sure though.
CaelanT said:
Sure she is the girlfriend and not you? LOL
Go get it back playa!
Click to expand...
Click to collapse
hahahaha!!
i'm sitting alone in a lounge/bar having an early dinner and I just started cracking up. people staring at me weird now.
haha. thanks.
I ran across another XDA thread stating that "neither odin or heimdall will work reliably it at all on Windows XP... but will work fine on Vista or Windows 7". Can anyone comment regarding their experience with Odin running on Windows XP? My desktop runs XP and I successfully loaded Kies (for my Captivate and Infuse)... but I've never loaded/used Odin. My SGS2 arrives in the next day or 2 and not sure if I want to risk flashing using Odin on a Windows XP platform. Thanks.
current laptop.... dead
so all i have is my old media hub which is like 2004. so yea xp SP3 here. used odin just fine. 1.82 or whatever its called. it was an odin3 download. also didn't effect my device at all, started half at home on my old machine, and flashed the cwm patch later at my parents on there vista machine