Related
Hi all,
I am unable to get Kies to recognise my galaxy s (when in Kies mode) or windows for that matter. I've tried installing the samsung usb drivers etc using the latest version of kies, still doesn't work.
What options do I have now in terms of firmware flashing? (I'm not installing 32bit xp just to flash my phone)
Cheers
if you search the forums you will find your answer, which will be along the line sof using Odin, very easy to use, so good luck and enjoy.
win7-64bit and kies connection semi-working method
I've tried almost all methods mentioned on different forums...but since i'm unwilling to mess to much around i've opted for this way:
using latest kies 1.5.3. 80something... on win7 64 bit..
remove the lockpattern from the phone if yo uhave it enabled
install kies...remove the kies autostart option and the kies trayagent
do the repair drivers and reboot
ones the bios screen is done..have the phone unlocked and connect to pc/laptop
wait and wait some more after login to windows..
one most occasions windows will finally tell you it have a new device ready for you...then open kies and life is good.. at least until like in my case the laptop goes into powersave mode and the connections are broken and I have to do the reboot step again
the firmware update from jf__ something to jm__ something was a hassle...but after a few attempts to run it the darn thing finally worked..
hope this helps
thanks for the help b, tried it but didn't work
I think the official word from samsung is that kies does not support windows 7 64.
Seriously regret ever getting this phone.
ardll said:
thanks for the help b, tried it but didn't work
I think the official word from samsung is that kies does not support windows 7 64.
Seriously regret ever getting this phone.
Click to expand...
Click to collapse
i am with win7 x64, fine here
using odin to flash rom is dam easy job.
Kies updated to _82 today.
the _82 update fixed closing the firmware updater for me that was in the last 2 builds on win7 x64 , it promptly closes having not used up more than 33mb ram when I click cancel or close after checking for new firmware, previously it billowed up to over 1300mb use and really flawed my system until it, kies and the connection manager were terminated fully.
http://www.samsung.de/de/support/detail.aspx?aguid=47e29085-4dff-4b5c-b8ab-dd9b9c8b70f8&dl=software
try the new PC Studio software for SGS
download link and detailed info on SGS wiki, click my link
So I got my tab today. But Win 7 x64 (i have 3 machines with x64 and none with x86 at home) doesnt recognize the device.
There are no drivers in the manager and nothing happens when i choose Kies on the galaxys usb connection menu.
Kies does see that the device is in storage mode, but if i change it to kies connect windows doesnt even give me the plug and play sound. Nothing.
EDIT:
The trouble was the non-stock launcher
Heres what to do if youre having troubles:
1. download Home Switcher from Market and set it to Touchwiz launcher
2. connect to Kies (im using 1.5.3.10092_58_8)
Proceed to root and enjoy!
I have the same problem but your solution does not work for me.
Well that's weird, I have a notebook with Windows 7 x64 and apparently the latest official version of Kies, haven't had a single problem for the Galaxy Tab to be recognized...
I'm not sure which version number I have: I have downloaded Kies on samsung.de, then after the installation I was prompted that an update was available, so I have installed the update of Kies.
Then I have connected the Tab to my computer in Kies mode, the drivers have automatically installed, and Kies recognized my device directly...
Same problem
running on vista 32 the phone isnt didectable trying to unistall the usb drivers and install another recommended one then will sea
Didn't work for me either. Also, btw. Kies is complete crap and does really intrusive stuff. Tmobile garbage apps permanently installed on the device, etc. I don't think I'll ever really understand what the product people think at these companies.
Rant over.
Anybody working on a root that's a little more direct?
Weird. Kies kept saying it didn't recognize the device, but the root app appears to have worked. Need to try an actual root thing to see if its for real.
Whoops. spoke too soon. Didn't actually root.
So just to be sure. It is ok to use Win7 x64 for Kies general use and more importantly to do any future software upgrades?
Its just that win7 is not a supported OS.
mea.samsungmobile.com/ENG/support/softwaremanuals/softwareKiesUpdate.do?phone_model=GT-P1000#how
Thanks.
vs2 said:
So just to be sure. It is ok to use Win7 x64 for Kies general use and more importantly to do any future software upgrades?
Its just that win7 is not a supported OS.
mea.samsungmobile.com/ENG/support/softwaremanuals/softwareKiesUpdate.do?phone_model=GT-P1000#how
Thanks.
Click to expand...
Click to collapse
I've been using it just fine with Win7 x64 for the last six months or so, for my Galaxy S devices, give or take the usual Kies bull**** that will happen on any OS.
Thanks. I see they just released new software which supports Win7.
mea.samsungmobile.com/ENG/support/softwaremanuals/software.do?phone_model=GT-P1000&sw_type=SW
Fixed! - Cannot install MTP USB driver
I had a problem when I plugged in my SGT in Kies mode for the first time the MTP driver failed to install and gave an error. Then Kies could not see the Tab.
Fixed it by uninstalling Kies, upgrading Windows Media player to latest version then re-installing Kies.
Read it in a forum somewhere and it worked first time.
Hope it helps someone else
In Ontario Canada with a Bell Galaxy Tab
And... none of the above solutions have worked for me... any other suggestions?
GREAT!!!with this trick finally i can connect my tab to the notebook!!thanks a lot...
I tried to unistall kies,reinstall kies,uninstall driver, reinstall driver, .........
but never Kies recognized my SGT.
But finally I've solved in this way:
- Disable usb debug mode
- Set usb to kies mode
- Lock the screen <-- very important step.If I don't do this, kies doesn't recognize my Tab
- Connect Tab via USB to my Win7 64Bit
- Start Kies
For reference:
I've a SGT rooted and latest version of Kies (2.xxxx).
Hope it helps someone else
limonxda said:
I tried to unistall kies,reinstall kies,uninstall driver, reinstall driver, .........
but never Kies recognized my SGT.
But finally I've solved in this way:
- Disable usb debug mode
- Set usb to kies mode
- Lock the screen <-- very important step.If I don't do this, kies doesn't recognize my Tab
- Connect Tab via USB to my Win7 64Bit
- Start Kies
For reference:
I've a SGT rooted and latest version of Kies (2.xxxx).
Hope it helps someone else
Click to expand...
Click to collapse
How do you set it to kies mode?
Simply, on SGT, go to Settings Menu
tap on wireless --> Usb and then select Kies.
thanks @limonxda, but your suggestion didn't work for me. KIES still doesn't recognize my Tab.
Does anyone have any more suggestions?
I have a verizon GTAB and they seem to have removed the KIES Mode from the selection.
I guess they want us to use their VCast software only.
I ended up fpashing my tab with roto fw and now it connects to kies just fine.
Sent from my GT-P1000 using XDA App
I know this thread is a bit old, but I wanted to say thanks for your posting here. I was having trouble getting Kies to recognise my Galaxy Tab. However, after switching back to the Samsung Launcher from LauncherPro, it has recognised my Tab and is installing some large firmware update (hopefully Gingerbread!).
Of course, it would be nice if it told me more specifically what it was updating....
EDIT: Scratch that. An hour of firmware updating and I still seem to be running 2.2. Or specifically, the cryptic firmware version from Kies is:
PDA:JJ7 / PHONE:JK5 / CSC:JJ5 (CPW)
I used to be able to put my Captivate in USB debugging mode and enable usb storage and move files perfectly. Now that I think about it the last time I did this was before I upgraded the Captivate to Android 2.2. So, I think something happened after upgrading now when I plug my Captivate I get a driver error and it says Code 43. I tried uninstalling and reinstalling drivers, but don't think it helped I even tried installing from Kies Mini. I am not really sure what to do here. Any help would be greatly appreciated because I really need to transfer some files from Captivate to PC and vice versa asap.
Thanks,
Mo
You should be able to transfer files without drivers installed.
Sent from my GT-I9000 using XDA Premium App
When I plug it in it says Driver Device Software was not successfully installed. and Windows has stopped this device because it has reported problems. (Code 43)
then USB Device not recognized pops up.
When I go to my computer there is nothing showing my device so how would I begin to transfer files via USB??
Sorry but am still somewhat new to driver issues and android
Not sure, sounds like your computer. Updating the rom won't cause usb errors.
Do you have wireless connection? If so, download FileZilla or some other ftp client to your computer. Then go to the market and download OnAir or some file server. Then you can use the wireless to ftp files back and forth.
That is until you figure out you computer usb troubles.
Yea I'm in the processs of transferring the files via bluetooth, but any advice or at least a place to start for fixing the usb problems. I honestly have had no problems since updating to 2.2 and cannot think of any changes I have made to the computer either
bump can anyone help?
I wish someone would step in here as I am having the exact problem - Win 7 - 64 Pro. All of a sudden the desktop PC has stopped recognizing the Samsung Captivate. It wasn't always this way and I cannot figure what may have changed on the desktop to cause this (except for MSFT updates of course).
win7
BUMP. I just used my home computer (windows xp) and reset my captivate, then rooted and flashed Andromeda. this is the first time i flashed a rom and everything, but everything went smoothly and I would like to try out other roms, but I am only home for 4 months out of the year
I USUALLY have my 64 bit Win 7 laptop, but it is still not recognizing my Captivate. I still cannot even mount it. If anyone can help it'd be greatly appreciated. I tried reinstalling captivate x64 drivers and tried samsung kies mini but no luck. can someone troubleshoot me or send me a step by step walkthrough. I am getting the same errors I have had earlier and like BillMc it wasn't always this way.
BUMP. I got the same issue and it is driving me nuts. Any help will be greatly appreciated.
Open Device Manager, plug in your phone, and see what new devices pop up when you plug it in. Then uninstall all "devices" related to the Captivate.
Then unplug your phone and reinstall the captivate drivers pack. Then plug your phone back in and see if your computer sorts out the drivers correctly.
This fixed my issues. Try it.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
rahbert said:
Hello ppls.
I've read some similar threads about this problem, tried some solutions, didn't worked and they didin't really had my situation.
So lets begin. My phone isn't recognized by my computer of anysort. When i plug the device i get this error: Windows has stopped this device because it has reported problems. (Code 43) .Tried solutions for the error with no succes.
I run Windows 7 64 bit,4gb Ram, Intel Quad Core 2,2 Ghz. I downloaded the drivers for the device from samsung, bummer when i manually try to update the drivers and set the path to where the drivers are it says The device is already up to date,even with online search.
What i've tried so far:
1. Tried in normal condition with KIES. Debugging off.
2. Debuggind on. Same
3. Different PC with windows 7 32 bits, same error, same solutions that don't work
4. Updating .Net framework
5. Installing a program that automaticly detects drivers. It didnt even see it.
6. Checking the cable for corrosion or anything else faulty. Cleaned it even.
7. Yelling are the stupid phone !!
Thank you.
Click to expand...
Click to collapse
Have you tried with a different USB cable?
No because i connected succesfully my friends galaxy fit with it, so the cable is not the problem.
thry manualy installing galaxy s drivers on pc?
Uninstall and reinstall the drivers.
Try different drivers.
Make sure you're using a Samsung wrong with the Samsung drivers.
Use a different PC.
Keep trying!
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
rahbert said:
I gave up...I tried everything.Spent hours of searching forums and applying solution, nothing works... Tried On 3 different pc's. 1 with win 7 64bit, and the rest win 7 32 bit. I can't manually install the drivers either. Says there are already up to date when i set a location for the drivers to detect...I can't even use it as mass storage.
Click to expand...
Click to collapse
To try using different drivers you would need to uninstall the current driver.
And just to be sure, you didn't flash to CM7/MIUI recently, not realizing Samsung drivers won't recognize your phone anymore, right? Nexus S drivers for those ROMs.
Its on the original ROM i think. Recently bought it second hand, 1 year old.
I couldn't find different drivers...except 32 bit and 64bit, but they all are the same version. Maybe post a link or something. Mine are 1.4.4.
Firmware version: 2.3.3
Baseband version i9000XXJVO
Kernel Version: 2.6.35.7-i9000xwjvh - CL184813 [email protected] #Dark_core_2.4 Mon May 16 15:02:38 EEST 2011
Build Number: DarkyRom JVH v10.1
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
rahbert said:
SOLVED. The problem was from the ROM Darky 10.2. I went to a service did a resoft donno how they do it, installed me the original gingerbread 2.3.4 and now works like a charm!
Click to expand...
Click to collapse
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
upichie said:
Just for future reference, this site is filled with tutorials on how to do just that. In fact, that is what this site is all about—new ROMs, new ideas, and how to get them onto your device. Look around next time.
Click to expand...
Click to collapse
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
rahbert said:
Dude i'm not the kinda of guy that doesn't research first. Like i mentioned i tried everything i found with no effect. The thing is, the problem reappeared after a day, with the new rom. Took it back to the service, said its a virus from some apps i installed...Is it possible? Thing is, it worked even after i restored all my apps.
I couldn't change the rom either because neither Odin or Heimdall saw my phone, if that is what you reffered to. If you know how to resoft a phone without the pc recognizing it (not even as a composite USB device in download mode or debugmode) and just Showing in Odin or Heimdall "Unknown Device" and failed at installing ClockworkMod, be my guest and redirect me to the tutorial, or tell me how to do it.
Thx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1347899
upichie said:
http://forum.xda-developers.com/showthread.php?t=1347899
Click to expand...
Click to collapse
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
rahbert said:
How can i use Mobile Odin if i can't root it?
Anyway the problem has been identified as the driver behind the usb slot of the phone, At least that what the guy at the service said...for the moment i'm waiting. I'll keep you posted.
Click to expand...
Click to collapse
Throw it against the wall then. You ask us for help, disregard all of it, and then update us on what the service desk told you. If you will only listen to them, then don't ask us, kay? Appreciated.
Hi, there.
Actully, the rahbert's question is not bad. How can i use Mobile Odin if i can't root the device?
Or, how can I root without PC? Is it possible? I have exactly the same problem:
Nexus S (I9020), ICS 4.0.4(stock). When I plug the device: the error is reported(Code 43).
Should I try wipe data/factory reset? I really don't want to do this, because there is another good question: How can I fully backup my data(Titanium and so on) without root access? Can you suggest me something? Thanks.
Herman76 said:
Have you tried with a different USB cable?
Click to expand...
Click to collapse
Changing the USB cable worked for me. Thanks!!
Ok ladies and gents,
I've been on a mission to root my Note 5 N920I for months now.
My problem is no computer will read/recognise the device. The Mac's seem to not even recognise it's plugged in, with Windows, no matter which driver I install it keeps telling me the "device descriptor failed blah blah blah". I managed to root my S4 very easily on Mac with Jodin3 so I know that it ain't no user error.
I've Googled and Googled ways to root without a computer or installing a custom recovery without root, but from what I understand I can't flash TWRP as recovery without a computer and therefore cannot root without a custom recovery.
I've Googled ways to fix the USB issue by making the xml file and putting it into the correct folder, but for that I need to be rooted. Right?
When she's plugged into a computer with USB debugging on or off nothing comes up in my notifications except for charging. I tried using the toolbox which I found on here (sorry can't remember the name) though it seemed like I was getting close, I couldn't get close enough before my temper got the better off me.
If my memory serves me correctly the OTG function worked when i first got the phone but didn't after the first update. My mate's Note 5 also has the same issue. I Googled it and seemed it was common issue on these phones.
I've tried to learn some Terminal/Command Prompt to see if I can fix it that way through Debian or whatever, only got as far as understanding it, kind of. Big ups to all you coders/programmers out there it really is an artform.
So PLZ PLZ can y'all help me, there has to be a way aside from setting this thing alight and getting a new phone.
My next mission, which I only embarked on a couple nights ago is unbricking my dad's Note 4 (N910G) that just hit the **** one day after spazzing out for a few days then would not turn on. I'm getting close though I haven't put much effort into that yet.
Any advice will be greatly appreciated, thanks in advance. ?
Anyone??
$pooLz said:
Anyone??
Click to expand...
Click to collapse
1)First of all have you enabled usb debugging and oem unlocking options enabled from developers options?
2)Install latest usb drivers for your model no on pc, use original usb cable to connect your phone
3) Try different usb hub-ports on your pc, it is recommended to use main-usb port to connect device properly which is mostly located backside of cpu cabinet
4)Does odin recognises ur device? If yes then you can flash twrp and cf autoroot both ( Sometimes Kies or smartswtich like programmes enforces device not be reognised, so uninstall them before trying to connect and flashing thorugh odin)
5)Try to update device drivers manually from Pc's administration
6) Try to connect your phone on another pc running windows and see if it recognises your device or not
I've tried all of that, i have a 09 Macbook Pro hand me down running Yosemite with Windows 8.1 Pro n just put Ubuntu on her today through Parallels. None of which recognise the phone being there.
I've plugged it into 2 HP PC's and both just keep telling "device descriptor failed". They're both kinda old too.
Unless someone has a specific driver they've made or found or could make me?? Clearly I'm a noob.
Closest I've found is https://github.com/452/USBHIDTerminal/wiki/How-to-enable-USB-host-API-support but still need root or system mounted as rw.
Any other ideas? Any ADB codes anyone could help me with ?