Hey everyone.
I'm running into a really annoying issue. I picked up the T-Mobile GS5 a couple weeks ago and rooted it shortly thereafter. That is the only mod I've done, but it obviously blocks OTA updates.
With the new (NE6) update stable, I want to upgrade, so am trying to use Kies. Unfortunately, I can't get it to work. Everytime I try, I get the "new firmware available" alert, but when I attempt to proceed, Kies just freezes. I've tried not using the auto-update and selecting "Firmware Upgrade" manually, but no difference.
I was originally trying on an XP virtual machine (VMWare Workstation under Linux), and thought maybe that was the issue so tried under a Windows 7 VM. Same issue. So I tried the Mac version of Kies on my MBP. This time, I got to the screen where you need to check off that you agree to the update terms, but when it begins to download, Kies loses connection to the phone and it eventually errors out. So I tried a Win7 bootcamp attempt, but same general Windows failure. So I tried a baremetal (on PC hardware) Windows 7 attempt, and I'm sitting here at a slightly grayed out Kies screen that is unresponsive. In each method above, I tried numerous times with reboots of the computer and phone.
I searched, but couldn't find any similar issues. Based on the number of attempts on different computer scenarios, I have to believe it's an issue with my phone, but outside of this it works great. I've tried disabling developer mode, rebooting numerous times (phone and computer), etc. etc.
Does anyone have any idea what could be wrong? I consider myself fairly adept at Android and have a lot of custom experience with Nexus devices, but am not super familiar with the intricacies of Samsung products.
I used the Odin root method, and see there are firmware packages to upgrade that way, but believe it would factory reset my device - correct?
Any help would be greatly appreciated.
Thanks.
I read that sometimes having an external SD card can cause issues. Just tried removing that since I did have one installed. No difference.
try right click and run it as administrator with Kies see it work or not, also download the NE6 firmware files from sammobile and use odin to flash it, it wont factory reset yr phone, only thing u will lose is root but it can re-root with same step u did before.
koolboyztn said:
try right click and run it as administrator with Kies see it work or not, also download the NE6 firmware files from sammobile and use odin to flash it, it wont factory reset yr phone, only thing u will lose is root but it can re-root with same step u did before.
Click to expand...
Click to collapse
Thanks, I did try that too but no difference. For some reason, my phone seems to be incompatible with Kies.
After a lot of frustration, last night I did manually upgrade using Odin and the firmware files in the stock zip thread over in the dev section here. Initially, I only did the 'firmware' upgrade, since it seemed that the 'full' package would wipe the device (based on the comments in that thread), but that actually caused a lot of issues (fingerprint reader stopped working, etc.). So I was forced to use the full one, and it worked without wiping my device, which I'm quite happy about.
I did lose root, but for now I'm good. I mainly wanted it to restore from TiBu, but haven't needed root since, so I'll leave it stock and try the next OTA update.
I'm just more concerned about why Kies failed on 5 different machines (virtual or physical).
Related
So after searching the vast horizons of XDA I haven't found an answer that really helped me. Nor have I found someone with this distinct issue. I have an unlocked Samsung Vibrant. I have not rooted it. I updated to J16 with that P.O.S. Kies Mini a few months ago. I hadn't noticed this problem until the last month or so but I haven't had time to sit down and curse at my computer long enough or offer supplications to Google until now. I've just been using Awesome Drop to get what few files I wanted onto my phone. I've had enough of that now. And...I also want to update it to Froyo but I can't do that if I can't get my computer to see my phone. I'm running a Toshiba Satellite A205 with Windows Vista 32bit.
I have checked the drivers and as far as I can tell, I'm using the right ones. I downloaded Kies Mini again today (I deleted it after I was finished with J16 because I wanted it as far away from me as possible) and it seemed to say something about downloading drivers as well. I tried plugging in my phone. Nothing new. So, I went in search of drivers again. I have searched and tried a few different ones but nothing has solved my problem.
The phone charges fine from my laptop. It hooks up immediately and charges without a problem. Unfortunately, my phone seems to regard the PC as a complex wall-wart. Debugging on/off, USB Settings on Mass Storage, Kies, or Ask on connection, it doesn't matter. It doesn't give me the option to "mount" as it has in the past. It doesn't do anything except charge. I've seen some people say it's a problem with their cables (I've only got one at the moment) but since my phone charges fine, how can it be a problem with the cable?
Only thing I hadn't tried was a factory reset. So, I sucked it up and tried that. Nope. No change. At this point I'm wondering if it's a hardware problem, not a software problem.
I'm out of ideas. Anybody else?
Well you can always root it, install ROM manager from the market, install clockwork recovery, download the ROM you want to install in flashable .zip format from your phone and flash away. A new ROM might fix your USB issue.
If you don't want to root it, see if you can get into download mode, and flash a new ROM using Odin. I would check with a different cable first, just to be sure that's not the problem though. It might save you some headaches.
If it was me, I would just root it and load a custom 2.2 ROM. I would also get Titanium Backup from the market and backup my apps and would do a nandroid backup from recovery before flashing anything new just to be on the safe side.
There's some good info on how to do most of that in this sticky post.
http://forum.xda-developers.com/showthread.php?t=849028
Is it just me or is Kies the absolute worst phone connectivity software in existence?
I have been trying to do the firmware updates via Kies since they were released but keep getting the same error message (DLL Load Fail). I have tried the update on 2 PCs - 1 running Vista and the other running XP. I don't have access to a Windows 7 PC to try it.
Don't get me wrong, I'm happy with the SGS2 and apart from the occasional random reboot, I don't have any complaints. I would just like to be able to apply the firmware updates!
I've read a few solutions on another thread about using Odin, but I'm new to Samsung phones and a bit wary about Odin. Though I did a lot of rooting and custom ROM installs on my old HTC Desire so I'm no stranger to messing about with android hardware via unofficial means...I just don't want to be unofficially messing too much with my SGS2 since it's less than 3 weeks old.
Does anyone have a non-Odin solution to the crappy Kies DLL Load Fail problem?
NOTE TO ADMINS: Apologies if I've posted this in the wrong place, please feel free to move it if necessary.
I had the same problem (DLL Load Failure after firmware download) on two of my computers (Windows 7 SP1 x64) as well. After a few tries (including computer restarts and Kies reinstallation), the problem spontaneously went away - without any preceding configuration change I can remember.
If you continue to have firmware update problems and don't want to resort to ODIN you could try if a firmware update via Kies Wi-Fi (Home Screen -> Settings -> Wireless and network -> Kies via Wi-Fi) is possible.
In general, I do agree - Kies is the worst. It is really puzzling why Samsung Android phones can't just update via cell network/wifi like HTC devices (or even the Samsung Nexus S).
babblerx said:
Is it just me or is Kies the absolute worst phone connectivity software in existence?
I have been trying to do the firmware updates via Kies since they were released but keep getting the same error message (DLL Load Fail). I have tried the update on 2 PCs - 1 running Vista and the other running XP. I don't have access to a Windows 7 PC to try it.
Don't get me wrong, I'm happy with the SGS2 and apart from the occasional random reboot, I don't have any complaints. I would just like to be able to apply the firmware updates!
I've read a few solutions on another thread about using Odin, but I'm new to Samsung phones and a bit wary about Odin. Though I did a lot of rooting and custom ROM installs on my old HTC Desire so I'm no stranger to messing about with android hardware via unofficial means...I just don't want to be unofficially messing too much with my SGS2 since it's less than 3 weeks old.
Does anyone have a non-Odin solution to the crappy Kies DLL Load Fail problem?
NOTE TO ADMINS: Apologies if I've posted this in the wrong place, please feel free to move it if necessary.
Click to expand...
Click to collapse
The answer is ODIN.
Seriously, just read it, read the SGS 1 forums etc... ODIN is what samsung use internally
I know this does not help you, but really, ODIN in 100 times more reliable and safer than Kies to update firmware. There are picture guides available right here on XDA.
also try running Kies update when you are freshly booted the phone in Airplane mode. Do not kill any tasks by ATK or in built Ram cleaner. Just boot > airplane mode> plug in and give it a try.
I have windows 7 and KIES is just soo slow, not tried updating firmware as have no issues with phone
(and not sure what improvements are included)
I have 2 computers and can only do certain things with either. One runs 7 64bit the other 7 32bit. One will work with Kies perfectly fine, and will run ODIN as well, but ADB is a complete no go.
The other will do ADB and Kies via Wifi, but nothing else.
Driver installation is the problem. One machine refuses to find drivers for SAMSUNG_Android and CDC_serial.
Works perfect for Me every time :-\. But odin works great too so to prevent any issues its prob best to use odin especially with all good support from xda
vimto25 said:
Works perfect for Me every time :-\. But odin works great too so to prevent any issues its prob best to use odin especially with all good support from xda
Click to expand...
Click to collapse
No problems with KIES on Win7 64bit
babblerx said:
Is it just me or is Kies the absolute worst phone connectivity software in existence?
Click to expand...
Click to collapse
No.
Itunes is
Absolutely agree it's shocking !
I have given up with Kies, but Odin is not working for me either!!!
It all seems to flash ok according mto Odin log, phone reboots, and then check the phone status and it's still at KDD firmware level ...
Any ideas what's wrong with Odin anyone?!
Martijnsmith said:
Absolutely agree it's shocking !
I have given up with Kies, but Odin is not working for me either!!!
It all seems to flash ok according mto Odin log, phone reboots, and then check the phone status and it's still at KDD firmware level ...
Any ideas what's wrong with Odin anyone?!
Click to expand...
Click to collapse
Lol this is exactly what I mean. People never doubt their devices. Oh kies doesn't work for me. There must be something wrong with Samsung and their crappy software. Oh no odin doesn't work either there must be something wrong woth odin too now. Kies and Odin work fine stop saying they don't. If it doesn't work the problem is on your end. How many freakin times... and I'm the one who is the troll here
Swyped from my GT-I9000 using XDA App
worst?....
its not great but itunes holds that crown by a country margin, had you forgotten about that?
er...
I never said Odin doesnt work, i was posting to try and get some useful tips on what i might be doing wrong rather than to receive mindless abuse.
And i am certainly not the only one with the Kies failure messages that seem to be rife.
Thanks for not even helping suggest what COULD be wrong on my side, which is exactly what i'm trying to find out. Troll
Posted this on the general discussion section but have had no replies, hopefully someone here can help?
Hi everyone, first, this is my first post, new to the forums, at least as a registered user. I have a problem with my phone. I know most of you are wondering why I have not just read the other posts on the forums, but I have. I have attempted every solution to the problem posted previously.
Background: Phone: Samsung charge.
I was being impatient and did not want to wait for the gingerbread update form Verizon. I flashed the leaked gingerbread 2.3.4 onto my phone using odin. Everything went great. I was able to use my phone with no problems except shortened battery life, but nothing major. About a month ago the battery life was impossible to maintain and there were some software bugs, like clicks during calls, startup taking forever, around 2 minutes on average!, and random restarts that never happened before. I decided to look up some fixes and found that verizon and samsung had released GB 2.3.6 for the charge. I got excited and decided I wanted to get that, but I could not via OTA. I read some forum posts and they mentioned attempting a factory reset on the phone then trying OTA update. I went ahead with factory reset and everything went fine. My startup time is around 25 seconds now and no random clicks or gliches, but still not on 2.3.6, which was the whole point. I then decided to just flash the stock 2.3.6 rom to the phone.
Problem: When I plug my phone in to multiple computers it will charge but not connect to the computer. This means on my Mac it does not show as an external drive, which it has in the past. On my windows 7 machine it says that drivers were installed but could not be used (I can get the exact quote if needed.) I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device". I have tried to enter download mode when hooked up to windows computers and no connection is found.
Possible solutions attempted and their outcomes:
1. As stated, I attempted the method shown in a thread on droid forums for installing the samsung drivers. I have attempted multiple times to install the drivers on my windows machine and the device remains "unknown".
2. I have attempted multiple cables on multiple computers, both mac and windows 7. No change.
3. I have installed adb and attempted to locate devices using adb devices command on mac. No devices found.
4. I have attempted all methods with both usb debugging checked and unchecked.
5. I have tried every possible usb port I have.
Ideas/questions I have had that I have no idea are possible or how to fix!
Would a factory reset take away the ability to connect to a computer from my phone. So, is there a piece of software in the build I have that controls the connection between the computer and the phone, an identifier of sorts, which is now missing, now that I have reset the leaked ROM.
Is there a way to flash a new ROM without connecting to a computer, via the sd card, and what is that? I have read some things in other posts but am too much of a n00b to understand most of them when using sdcards.
ANY help will be greatly appreciated. PLEASE PLEASE PLEASE!!! I have been at this for at least 6 hours, sifting through forums, searching google, attempting fixes that others have stated worked for them, only to fail every time. Thank you all.
have you try on a different pc?
maybe on your PC there is some problem with the drivers.
Moreover to connect via
adb u must enable Debug mode on your device in the application menu.
To flash kernel or other directly from your sd you can use the clockwordmode, but to install it you must before
install it and i fear you must use your cable connection
Sent from my GT-I9100 using XDA App
I have tried multiple PCs and a mac, even windows on bootcamp. I have installed drivers on every one, even uninstalled and reinstalled on one. One PC, my laptop was a fresh windows install (it was a linux box but I needed windows to use Odin). I was in debug mode and not in debug mode when attempting adb. Thanks for the suggestions though. As I said, I have tried numerous things and am completely stuck! so frustrating!
"I attempted to go into device manager and solve problem that way but it shows my phone as "unknown device"
Exactly there... you can try to force device to install a different driver.
Double click the unknown device then driver then update driver then find software in your computer then choose manually from a list of device drivers in your computer then show all devices you should see "android adb interface" or something related to google or android.
Try it... i hope this can help you.
Hi can anyone help me I have unlocked my phone to all networks but have been told if I update via Kies
it will lock my handset back to previous carrier ( T Mobile )
I really want to update my os and can't find a way of doing it any help or pointers would be appreciated.
Currently running 2.3.4
kernel I900XXKG1-CL349526
Build GINGERBREAD,XXKG1
You can upgrade to ics and pay to unlock.
If it was me,Id upgrade to 4.0.3 by flashing an unbranded firmware from sammobile(for my region).
Then root,then nand/efs backup,then use one of the free unlock apps on here/play(if required).
Rachmats ics rooting
Odin
Hktool
Helroz unlock
Triangle away
Then Id stick on rootbox/dremkernel.........lol
I have already downloaded firmware from Sam's, phone is currently connected via odin flashing firmware.
This has been running for about an hour now, thou there are still signs of action on my laptop HD.
how long should this process take ?
10 mins tops.
Disable kies and try.
I hope in the last 2 hours youve done some reading about the stuff I listed rather than diving in and ballsing things up.
I have disabled kies and tried again thou it looks like it's still not having it.
Half of what I have been reading is only starting to make sense now i'm getting my head around all this.
If you flash any rom from this site or samfirmware should not lock your phone again. It will stay unlocked.
If only I could get one to load up, fortunately I haven't bricked my phone thou I appear to have an ADB driver issue.
Only noticed this when using a later version of odin, I found a guide relating to this issue, I will give this a try shortly, fingers crossed.
It would appear I have an issue with the ADB drivers.
I have done a fresh install on another laptop, installed Kies looked for updates still no joy.
Then I even tried Heimdall 1.3.1 for os x no joy there either.
Now I am looking into finding and installing the ADB drivers from another source,
I have also tried downloading drivers from sammobile no joy there either.
Can anyone give me some advice on this.
I am trying now to install drivers in compatibility mode with xp. i'm currently running vista.
I checked properties in device manager and status of ADB is > This device cannot start (code 10)
This driver only shows when phone is attached via USB, I have tried to update via device manager
Still no joy
Finally having wiped my laptop and reinstalled windows, installed drivers, odin, connected phone,
I got a pass, 3 roms a CF root later, I settled for an unbranded UK ICS 4.0.4,
rooted phone with appropriate CF kernel,restored data. Tidy, well worth the effort.
Hi all. So I just picked up a Verizon Note 2 today and happily looked forward to rooting it. I'm on 4.1.2 Jellybean VRAMC3, model number SCH-I605. I'm afraid I may have messed something up.
I had downloaded Odin and installed the Samsung USB drivers and all that good stuff. Odin picked up the phone and all that, but a bit more looking around seemed to indicate that the usual Odin method of rooting wouldn't work on the latest version that I had.
So I downloaded the CASUAL installer and got that to run. It ran through the install, rebooted the phone, and then said it was waiting for Windows to recognize the device again so that it could continue with the install.
At that point, Windows informed me that a driver install had failed and the CASUAL install did not proceed any further, despite waiting a good 5-10 minutes.
Since doing this, the phone has had bizarre USB connection issues. Odin and Kies do not read the phone at all. Plugging the phone in brings up an additional drive for about two minutes with a Verizon Assistant Manager EXE, a USB Drivers EXE, and a couple other things, then it disappears.
The phone will often display a message informing me "Unable to find software on your PC that can recognize your device." This happens regardless of being in USB Debugging mode or not.
I've tried uninstalling and reinstalling several versions of Samsung's drivers as well as Kies. I also tried a factory reset on the phone itself, but these connectivity issues (and accompanying warning messages) persist.
Not sure how to proceed from here and would love a bit of help. Thanks!
Additional notes: All normal functions of the phone are working fine, and the computer DOES detect the phone as a "Samsung Android Device", but as stated Odin and Kies are not able to detect/connect with it.
Update: Messed with drivers a bit more and Odin will now pick up the phone again. When the phone disappears as a "drive" with install helper stuff, it reappears as a portable device, and I can browse the innards of the phone to put music and other stuff on it. CASUAL however still does not pick up the phone.