I tried to use the previous version of kies to upgrade my gs2 but it never worked. Update would be from:
[KF3/phone:ke7/csc:KD1] to [KI4/phone:KI1/csc:kh2]
Which I'm sure is a big step forward as I haven't been able to update forever. I thought that once I updated Kies I'd finally be able to update my phone. Now when I connect my s2 and hit update firmware, as soon as it asks to backup it loses the connection to the s2. I've reinstalled drivers twice to no avail.
Does Kies just blow as a software or am I doing something wrong.
Kies blows big time - utterly useless... useless at upgrading, useless at backing up. According to their twitter @samsungkies - "Seamless experience with Smarter Kies". That's a joke of a statement. Go with Odin my friend, much less aggro and it works all the time.
^ I so much agree to that post.
Kies never worked for me, not even when my SGS II was used with the stock rom that shipped with it. While there was an update out for quite a long time (> 1 month) it still was showing my version as being current.
Odin is so much better or just as simple: flashing from CWM.
husaam said:
Kies blows big time - utterly useless... useless at upgrading, useless at backing up. According to their twitter @samsungkies - "Seamless experience with Smarter Kies". That's a joke of a statement. Go with Odin my friend, much less aggro and it works all the time.
Click to expand...
Click to collapse
I briefly looked at Odin not too long ago, it looked sort of confusing. I'm in another country currently and spend most of my time either (50+ hours a week) working on projects here or exploring the country. As such I don't have much time to learn a new program if it's too confusing. But I'll give it a try and hopefully get to say goodbye to kies forever.
edit: Do I need to root* my s2 to use odin?
aDroidtoRemember said:
I briefly looked at Odin not too long ago, it looked sort of confusing. I'm in another country currently and spend most of my time either (50+ hours a week) working on projects here or exploring the country. As such I don't have much time to learn a new program if it's too confusing. But I'll give it a try and hopefully get to say goodbye to kies forever.
Click to expand...
Click to collapse
It's actually quite simply. Most ROMS come with only one file. That can be flashed via PDA. Do NOT, I repeat, do NOT, I repeat once again, do NOT, and again: do NOT! tick ANY option in ODIN, unless stated specifically in the ROM's instructions and even then tripple check that you're really about to flash a SGS II firmware.
So as long as you get the right firmware, do not tick anything and just flash it via PDA you should be quite safe. There's always a minimal risk, even if you do everything right but it's very very small.
Try This!
RUN Kies onces its loaded connect phone it will say connecting phone within a short period of time and error message will load, click onto the error message a new window will open, now it will have something like 4 stages. 1st stage will say disconnect cable from phone, once you have done this click on next or the follow up stage. Now this will or should Repair drivers, and now install drivers again once this has been done connect phone and phone will now load in Kies.
XP users may have to reboot PC for driver take effect.
Hope this hepls you.
PS:THIS problem only happen to me on live update, download new kies manually install no problems. Win 7 64bit
Looking at Odin for the first time can be a bit confusing. Once you know the score tho its very easy and quick. Flashing intras files for example is a complete doddle as it's 1 tar file
Sent from my GT-I9100 using xda premium
Nyssa1104 said:
RUN Kies onces its loaded connect phone it will say connecting phone within a short period of time and error message will load, click onto the error message a new window will open, now it will have something like 4 stages. 1st stage will say disconnect cable from phone, once you have done this click on next or the follow up stage. Now this will or should Repair drivers, and now install drivers again once this has been done connect phone and phone will now load in Kies.
XP users may have to reboot PC for driver take effect.
Hope this hepls you.
PS:THIS problem only happen to me on live update, download new kies manually install no problems. Win 7 64bit
Click to expand...
Click to collapse
I've reinstalled the drivers using the connection error troubleshoot, and the phone connects fine to kies. It just loses connection to kies when I try to update the firmware. When I have more time I will most likely just use Odin but I don't want to root my phone in order to do it. Is rooting necessary?
Once you get your head around Odin, its a piece of cake.
Look for Intratech's Official i9100 Firmwares thread in the Original Android Development section, you'll find everything you could possibly need in there (instructions, firmwares etc)
aDroidtoRemember said:
I've reinstalled the drivers using the connection error troubleshoot, and the phone connects fine to kies. It just loses connection to kies when I try to update the firmware. When I have more time I will most likely just use Odin but I don't want to root my phone in order to do it. Is rooting necessary?
Click to expand...
Click to collapse
OK Odin is easy just read the Q&A
link pls...
i just upgraded to 2.1 also and now can't upgrade firmware, just keeps looping in disconnecting and reconnecting never upgrading firmware
Since nobody answered yet... No u don't needa root to get Odin work
Sent from my GT-I9100 using Tapatalk
i have had the same connect - disconnect or backup problems with kies (my version is 2.0.3) and have always blamed it on kies but once i tried to restart the phone, everything worked smoothly and i could do all kinds of operations with it. My phone is rooted and the current fw version is XWKJ1 original.
Sent from my GT-I9100 using XDA App
mertakb said:
i have had the same connect - disconnect or backup problems with kies (my version is 2.0.3) and have always blamed it on kies but once i tried to restart the phone, everything worked smoothly and i could do all kinds of operations with it. My phone is rooted and the current fw version is XWKJ1 original.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
you're are correct for 2.0.3 but the new 2.1 is totally screwed up, crashed my windows even
Gavin.csy said:
i just upgraded to 2.1 also and now can't upgrade firmware, just keeps looping in disconnecting and reconnecting never upgrading firmware
Click to expand...
Click to collapse
Just read a solution that works for me on the Dutch tweakers.net website:
- In Windows fully uninstall Kies.
- Download the latest Kies version and reinstall.
After that the upgrade worked for me.
janderk said:
Just read a solution that works for me on the Dutch tweakers.net website:
- In Windows fully uninstall Kies.
- Download the latest Kies version and reinstall.
After that the upgrade worked for me.
Click to expand...
Click to collapse
do you have the link for the download, i still find 2.0.3 only, nothing directly 2.1
Windows 7pro (32bit) absolutely none of the problems listed here or on other threads (regardless of stock/custom anything) but.. Odin is easy if you follow instructions and seems much more reliable (see intratechs thread in dev section for instructions)
Sent from my GT-I9100 using xda premium
It finally worked for me, i don't know what happened why it suddenly decided to work/
One difference i noticed is i got a notification 'Samsung Modem succesfully installed' which i did not get for the past 2 hours of restarting,uninstalling ,installing. It just suddenly came when i connected the phone
Kies is really crazy as hell
I think you may just have to turn off your anti-virus/firewall software while you update. It worked for me.
Related
There is a devil in disguise called Kies, which Samsung has unleashed on its victims (customers).
The internet is full of it! Google 'kies' and you Will find only problems from the first page itself!
Don't know what Samsung had in mind when it was released. Working on it is like a hurdle race and the normal user isn't an athlete! Even if you pass on hurdle somehow, another one is waiting for you with a big grin. There is no alternative. Use Odin and your warranty's in trouble.
I have been trying to upgrade my GT-I9000 to 2.2 for days! First Kies won't detect my phone. I tried deleting files with long extensions but it didn't work. After many more alleged solutions I finally had to hunt down all Kies files and registry keys. Reinstalled Kies and it worked. But this was not the end of the story! It detected the phone but won't upgrade it!
"This device firmware cannot be upgraded!!"
Why??
Even the Samsung people did not have the answer.
Another series of possible solutions and finally one worked!
But again this was not the end. Halfway through the firmware download came the 'Cannot connect to remote server'. Only once it had brought misery but it came again, and again, and again.
And until now the end user still lies in vain.....
You came here to complain about Kies.... ????
Dude, just flash it urself, it's easier and safer ....
I would never use Kies to upgrade, hell NO... But goodluck..... U ginna need it
Sent from my GT-I9000 using Tapatalk
search on here for Kies Reg Hack and spoof the product code as XEU, then re-connect and it will give you the update.
or just do it the odin way as previously suggested.
Odin, definitely
Use Odin. Got Froyo in my GT I9000 yday with it.
Kies is the worst piece of crappy software I've seen.
Cheers,
Roger
1. Begin here
Use this method heimdall
2. Then here
3. Finally here
Hope this helps...
Fremen567 said:
You came here to complain about Kies.... ????
Dude, just flash it urself, it's easier and safer ....
I would never use Kies to upgrade, hell NO... But goodluck..... U ginna need it
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Dude, I'm just highlighting Samsung's deeds. Let it be a warning to all who read to stay away from Kies!
Sent from my GT-I9000 using XDA App
kunjar said:
1. Begin here
Use this method heimdall
2. Then here
3. Finally here
Hope this helps...
Click to expand...
Click to collapse
Thanx kunjar!
That sure helps a lot!!
Sent from my GT-I9000 using XDA App
Turbokat said:
There is a devil in disguise called Kies, which Samsung has unleashed on its victims (customers).
The internet is full of it! Google 'kies' and you Will find only problems from the first page itself!
Don't know what Samsung had in mind when it was released. Working on it is like a hurdle race and the normal user isn't an athlete! Even if you pass on hurdle somehow, another one is waiting for you with a big grin. There is no alternative. Use Odin and your warranty's in trouble.
I have been trying to upgrade my GT-I9000 to 2.2 for days! First Kies won't detect my phone. I tried deleting files with long extensions but it didn't work. After many more alleged solutions I finally had to hunt down all Kies files and registry keys. Reinstalled Kies and it worked. But this was not the end of the story! It detected the phone but won't upgrade it!
"This device firmware cannot be upgraded!!"
Why??
Even the Samsung people did not have the answer.
Another series of possible solutions and finally one worked!
But again this was not the end. Halfway through the firmware download came the 'Cannot connect to remote server'. Only once it had brought misery but it came again, and again, and again.
And until now the end user still lies in vain.....
Click to expand...
Click to collapse
before you move to other method, did you try KIES 2.0?
Kies 2.0 suck.............so iTunes-ish!!!! but it is ok for me...the problem is the system performance!!!
Yes
bsamurai said:
before you move to other method, did you try KIES 2.0?
Click to expand...
Click to collapse
I have an updated version of kies
Funny. It always worked for me.
Sent from my GT-I9000 using XDA App
Same here, never really had any problems with KIES. I've flashed numerous times using the reg hack.
I use ODIN only for kernels and modded ROM's.
However, to use ODIN I always have to use my laptop (WinXP) as it gives errors on my desktop PC (Win7).
No problems with Kies here as well, but rejoice ... with 2.2.1 and higher, you can get OTA updates on your SGS.
Dread using kies.it doesnt work on one computer its bricked my other computer.
rtoussaint said:
No problems with Kies here as well, but rejoice ... with 2.2.1 and higher, you can get OTA updates on your SGS.
Click to expand...
Click to collapse
Didn't know that, any idea on how you should get the updates (when one is available )?
ota = over the air, which means u download with our phone, no need for pc.
now u need 2e recovery to do that now, because the update has to be signed by samsung(i could be wrong with this, as I didn't use it)
Sent from my GT-I9000 using XDA App
Sysiphus1981 said:
ota = over the air, which means u download with our phone, no need for pc.
now u need 2e recovery to do that now, because the update has to be signed by samsung(i could be wrong with this, as I didn't use it)
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thanks for the info!
.
Those who did not have any problems must be the luckiest people on Earth!
I had problems with every install on all my machines.
Well im using odin to flash stock firmwares on my phone. Just using Kies for samsung drivers, is that ok?
Only problem I've had with KIES is that I have to plug in my phone before I start KIES or it won't find it. My experience with the software has been mostly positive.(That goes for the old and new versions of KIES)
Regards
Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
[update]
This is likely a windows problem, not a problem with FB27. Sorry for causing any panic
few questions
what version of odin/are you using the self-extracting auto odin back?
http://forum.xda-developers.com/showthread.php?t=1433101
have you removed the kies/samsung drivers, then reinstalled? if you're having problems and it's related to the drivers (which it may be), sometimes you have to remove not just reinstall.
also, have you tried a different usb cord? sounds stupid i know, but they get **** stuck in the ends, or otherwise damaged, and cause weird issues in situations like this but otherwise work fine.
i just odined back last night using the package in the thread above, and it worked fine.
Just to make sure, you do have samsung kies installed, right? You need their drivers.
exabrial said:
Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
Click to expand...
Click to collapse
From your post you're trying to do the odin all in one self extractor... have you tried just using odin to flash the EL29 stock recovery repack and then flash through CWM from there?
http://forum.xda-developers.com/showthread.php?t=1390393&highlight=rogue
http://goo-inside.me/kernels/TeamRo.../rogue_ET-recoveryonly-1.1.4-rc0-odin.tar.md5
exabrial said:
Hey guys,
I installed FB27 + radio through CWM. I was previously on EL29. I want to get back to EL29, so I did the following:
Boot into windows (daily driver is osx)
Put phone into DL mode
Start Odin-oc el29
connect phone to usb
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
So i closed out everything, then opened Kies. It said it had an update, so I installed it, which included some driver updates.
I retraced my steps from above.
I tried installing the samsung driver package, still nothing.
Odin was working just fine before, and I hadn't changed anything in windows. I don't even use windows unless i'm using odin!
Any help is appreciated, I would like to get back to EL29!
Click to expand...
Click to collapse
If regular ODIN is working fine, look in the 2nd post, section #A2. There are regular ODIN packages for EL29.
http://forum.xda-developers.com/showthread.php?t=1433101
Personally I would try to figure out why ODIN OneClick isn't working because it might indicate some problem, but I understand if someone wants the quickest solution.
Use another cable besides samsungs crappy pos
Sent from my SPH-D710 using Tapatalk
Also try a simple reboot. Sometimes if I run sfhub's one click then Odin I have to reboot in between but only sometimes
Sent from my Nexus S 4G using xda premium
sfhub said:
If regular ODIN is working fine, look in the 2nd post, section #A2. There are regular ODIN packages for EL29.
http://forum.xda-developers.com/showthread.php?t=1433101
Personally I would try to figure out why ODIN OneClick isn't working because it might indicate some problem, but I understand if someone wants the quickest solution.
Click to expand...
Click to collapse
I have used EL29, EG30 of yours several times without any problems sfhub. I don't know why I occasionally need to reboot in between one click and regular Odin but its no big deal. 90% of the time I dont
Sent from my Nexus S 4G using xda premium
exabrial said:
watch as nothing happens, then windows says, "Unrecognized device (code 42)"
Click to expand...
Click to collapse
According to Microsoft, code 42 means there is a problem with multiple instances of the driver and the solution is a reboot (as John pointed out)
My theory as to why it is happening is there is a problem either in the USB driver or in ODIN OneClick with shutting down the USB bus when the flash is done, so next time you run it there is already an instance. Another possibility is if you use different USB ports on the computer between sessions, then the USB driver might get confused and keep multiple instances.
http://support.microsoft.com/kb/310123
Code 42
Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)
Recommended resolution
A duplicate device was detected. This error occurs when a bus driver incorrectly creates two identically named sub-processes (known as a bus driver error), or when a device with a serial number is discovered in a new location before it is removed from the old location. You may be able to resolve this problem by restarting your computer.
Restart your computer
Click Start, click Shut Down, and then select Restart in the Shut Down Windows dialog box to restart the computer.
Click to expand...
Click to collapse
Ok, so the best thing to try then is to uninstall Kies and the samsung driver package. I'm a windows nub, (I've haven't used windows since 1999) how do I make sure that any existing drivers that have been installed for a particular port are also wiped out? My fear is that removing kies won't remove any drivers that have been installed against a particular device... or is that not true.
exabrial said:
Ok, so the best thing to try then is to uninstall Kies and the samsung driver package. I'm a windows nub, (I've haven't used windows since 1999) how do I make sure that any existing drivers that have been installed for a particular port are also wiped out? My fear is that removing kies won't remove any drivers that have been installed against a particular device... or is that not true.
Click to expand...
Click to collapse
I don't think you should have to do all of that. Where EXACTLY are you in the process?
Sent from my SPH-D710 using xda premium
JohnCorleone said:
I don't think you should have to do all of that. Where EXACTLY are you in the process?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Same as my initial post. I'm currently at work Just trying to develop a POA.
According to MSFT, the error code 42 is not a problem with driver installation. It is a problem at runtime with multiple instances of the driver.
Did a reboot not work? Perhaps there are problems with the driver in the 64-bit and 32-bit locations?
I've rebooted the crap outta it already...
Anyway, uninstalled Kies, and samsung drivers package, and QPST for the hell of it. Rebooted, reinstalled Kies, now I get Error code 43...
I tried "search for a better driver" and pointed it to the samsung kies folder to no avail.
exabrial said:
I've rebooted the crap outta it already...
Anyway, uninstalled Kies, and samsung drivers package, and QPST for the hell of it. Rebooted, reinstalled Kies, now I get Error code 43...
I tried "search for a better driver" and pointed it to the samsung kies folder to no avail.
Click to expand...
Click to collapse
Are you on 64-bit? Sometimes the drivers need to be placed in the 32-bit location.
Have you gone over the general USB connection troubleshooting here:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Sorry, I go through a lot of threads and PMs so sometimes lose track of what people tried and didn't try.
I'm not at all experienced with Mobil ODIN, but wouldn't it be possible to forego the computer completely to get back to EL29?
It depends on the situation. In this case, probably yes. Mobile ODIN needs your phone to be able to boot into Android and needs you to be rooted, which the OP probably is. ODIN can handle situations where your phone won't even boot into Android.
sfhub said:
It depends on the situation. In this case, probably yes. Mobile ODIN needs your phone to be able to boot into Android and needs you to be rooted, which the OP probably is. ODIN can handle situations where your phone won't even boot into Android.
Click to expand...
Click to collapse
True, but he doesn't sound soft bricked, which is why the thought crossed my mind.
sfhub said:
Are you on 64-bit? Sometimes the drivers need to be placed in the 32-bit location.
Have you gone over the general USB connection troubleshooting here:
http://forum.xda-developers.com/showpost.php?p=19443755&postcount=142
Sorry, I go through a lot of threads and PMs so sometimes lose track of what people tried and didn't try.
Click to expand...
Click to collapse
It's quite alright, I appreciate the help. I followed the directions in that post, and am getting the same problem... It is windows7 64bit. basically, installed the drivers to C:\Program Files (x86)\Samsung\USB Drivers
I guess I'll try mobile Odin... windows hasn't improved any over the last 10 years I see.
Can someone help me I have the same problem it happened to me about a week ago when i tried flashing one of calk's rom and then all i know is that triangle disappeared from the samsung animation and then my computer will not recognize it.I've looked here and google and cannot find a solution!!!PLEASE help me!!I've noticed people with similar problems but no help.
Also I got mobile odin and tried to unroot but I am afriad I wont be able to root again since it will not discover my device.
Previously I had installed on my phone (I believe, but could be mistaken) a Twilight Kernel and Hurricane v1.6 Rom. Well, I had nothing but problems with the rom, and put up with them for some time, just because I didn't have time to go through and find a rom I liked and flash it. I decided to do just that yesterday.
Apparently my mind broke and I did something wrong (probably numerous things). I had first attempted to put the shiney new CWM9 with Shadow Kernel on, rather, I made the mistake of trying to just put the Shadow Kernel on after having done a full (triple) wipe on my phone. I got the boot loop for the kernel since there was no rom (duh) loaded. Okay, no problem, I'll toss a rom on the SD and boot into CW3 and flash it? Yeah, not so much. I got a short "Samsung" logo boot loop and could not get into CW3 after that.
So, I Odin'd it back to EL30, thinking I'll just start from fresh, right?
Wrong.
Next in the series of mistakes I made, I forgot that I had already downloaded and installed the Samsung drivers (don't ask, my brain was apparently on leave yesterday) and attempted to re-install them. They did not like this and would not progress and I had to End Process the install from Task Manager. I then uninstalled the drivers completely fearing that I may have corrupted them by trying to re-install and then EP'ing them.
I then re-installed them, or so I thought. Plug phone in and start again with One Click Root. Fail. The script couldn't find my device.
Hours of searching and trying different things later, script still couldn't find my device, though I now have both the phone recognizing there is a USB connection, and the computer has stopped yelling at me that there are no drivers (I believe it finally gave up and installed the Windows drivers for it). But still can't get it rooted or do anything but stock stuff.
So..
1:Samsung drivers won't install, running Windows 7-64 Ultimate; error at end of install just states: "The MMS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones v1.3.450.0."
2hone previously recognized USB Debug mode, but no longer. Will only Recognize standard USB connection, and with the connection made to PC, the script will not recognize the device.
3:adb for all intensive purposes does not appear to be loading..per the message from the script "Root was not obtained after 60 seconds. Make sure the phone is connected and that adb is working. If adb shell isn't root, reboot the phone and try the script again." I've rebooted numerous times, but I'm pretty certain that since it's not going into Debug, it's just not being recognized.
I have even tried Gingerbreak with no luck, just continuously sits on the rooting screen, but never proceeds (upwards 45 minutes I let it go).
Please please please please help me fix all the mistakes I did and get this thing working again and get the damned drivers installed proper.
(Baseband-S: D700.0.55.EL30, Kernel version 2.6.35.7, Build number: Gingerbread.EL30)
Note* I am happy with any root/kernel/rom at this point, I don't care, I just want the damned thing rooted again.
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Qbking77 youtube him...
Or I could do it for you remotely via teamviewer... either way
Sent from my SPH-D700 using xda premium
AtrophiedAnnie said:
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Click to expand...
Click to collapse
If you are up and running EL30 just Google How to Root Samsung Epic on EL30 and a qbking77 youtube video will pop up and all the links are there as well for the files you need. If you are not up and running then you need to go into the Roll Up sticky thread in Development and click on How to Restore a semi-bricked Samsung Epic....all links are there for that including 64bit drivers.
Sent from my SPH-D700 using xda premium
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
AtrophiedAnnie said:
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
Click to expand...
Click to collapse
Sounds more like serious root rust to me. Gotta keep up...lol. Samsung tries to make it harder to root...that works for 5 minutes around here...LOL.
Sent from my SPH-D700 using xda premium
IT'S DONE!!! Again thank you both so much1
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul
premington said:
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul
Click to expand...
Click to collapse
First u got check USB debugging ON (on the phone)
disable anti virus on the pc/laptop
kies will put your phone into download mode and will take awhile (Kies is super slow) for good reasons
Also consider rooting your phone and install custom recovery (CWM) and flash all the rom(s) you wish [if that's an option]
hit Thanks if i helped
Thanks for the help, Sam.
I'll try it again with the virus protection off. I disabled the Windows firewall and that did nothing. I've tried it about 12 to 15 times, which takes a long time because Kies takes so long to download what it needs.
Can I root a T-Mobile phone? I used to have a Motorola Atrix 2 and rooted that and did manual firmware and ROM upgrades, but that was an unlocked and rooted phone. I'm afraid I may screw up the phone or my T-Mobile service by rooting it and doing custom installs. Does anyone have experience with this on a T-Mobile phone they purchased at T-Mobile? I don't want to mess the phone up.
At this point, I think that's the only way I'm going to go Jelly Bean on my wife's phone.
-Paul
Rooting your s2 is simple and easy to do. Go to the dev section and look at the threads on how to do it.
You will use Odin to flash a custom recovery such a TWRP whick will install supersu. At that point you can flash the ROM of your choice and not have to deal with Kies anymore.
Hope this helps
Sent from my SAMSUNG-SGH-T989 using xda premium
use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like
sam.balia1012 said:
use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like
Click to expand...
Click to collapse
This is all great information... Thanks so much. I've pressed "Thanks" to each of you. :good:
-Paul
Hello,
I know you're probably thinking, "omg another note bricked thread". Yes, but I spent many hours of research and couldn't find a thread with my exact problem.
A little background:
I rooted my phone and everything was fine and dandy. I let a friend borrow my phone for a minute and they decided that it would be funny to uninstall google play. I installed the apk from online and had nothing but problems. The app would crash as soon as i started downloading anything. I looked into solutions and did everything from editing the host file to wiping the caches. Nada. The "solutions" just caused other errors. I decided to wipe and reinstall from my backup.
I realized after that because Google Play is a system file, my restore was useless. I decided to wipe everything and reflash the stock firmware with Odin. I downloaded the right one for the verizon model on 5.1.1. Odin sent the file to the device. Just before finishing there was an error and the phone rebooted anyway.
Upon booting the phone now lacked an OS and gave the "use the verizon repair assistant to reinstall the operating system" message. I tried the software (from a friends s5) on 3 different computers and it wouldn't work on any.
I figured, no problem, I will just reflash to stock with Odin again. Only this time my computer no longer recognizes the phone when I put it into download mode. Ive installed and reinstalled the drivers, changed the order of connecting the cables, and when the phone is booted. Nothing works.
The phone can only boot regularly (but lacks an OS) or go to download mode. Recovery doesn't work. Any ideas? Help would greatly be appreciated as the nearest phone repair center is close to 40 miles away
Tl;dr
Phone doesnt have an OS, can boot to download mode, but isn't recognized by computer. The basic troubleshooting steps haven't worked.
Hi urban.. I'm not to technical, but was reading your post. I hit a little confused... Your using the s5 Verizon recovery, not Odin image right
Also try uninstalling the Windows drivers and reinstall after you connect to computer
Sent from my SM-N920V using Tapatalk
Bern612 said:
Hi urban.. I'm not to technical, but was reading your post. I hit a little confused... Your using the s5 Verizon recovery, not Odin image right
Also try uninstalling the Windows drivers and reinstall after you connect to computer
Sent from my SM-N920V using Tapatalk
Click to expand...
Click to collapse
I tried the verizon recovery for the S5 (I don't have it for the note) and the software wouldn't load. Originally I reflashed the phone with an Odin image but now Odin doesn't recognize the phone.
Yup, I've tried that many times on different computers. Thanks though.
Urban415 said:
Hello,
I know you're probably thinking, "omg another note bricked thread". Yes, but I spent many hours of research and couldn't find a thread with my exact problem.
A little background:
I rooted my phone and everything was fine and dandy. I let a friend borrow my phone for a minute and they decided that it would be funny to uninstall google play. I installed the apk from online and had nothing but problems. The app would crash as soon as i started downloading anything. I looked into solutions and did everything from editing the host file to wiping the caches. Nada. The "solutions" just caused other errors. I decided to wipe and reinstall from my backup.
I realized after that because Google Play is a system file, my restore was useless. I decided to wipe everything and reflash the stock firmware with Odin. I downloaded the right one for the verizon model on 5.1.1. Odin sent the file to the device. Just before finishing there was an error and the phone rebooted anyway.
Upon booting the phone now lacked an OS and gave the "use the verizon repair assistant to reinstall the operating system" message. I tried the software (from a friends s5) on 3 different computers and it wouldn't work on any.
I figured, no problem, I will just reflash to stock with Odin again. Only this time my computer no longer recognizes the phone when I put it into download mode. Ive installed and reinstalled the drivers, changed the order of connecting the cables, and when the phone is booted. Nothing works.
The phone can only boot regularly (but lacks an OS) or go to download mode. Recovery doesn't work. Any ideas? Help would greatly be appreciated as the nearest phone repair center is close to 40 miles away
Tl;dr
Phone doesnt have an OS, can boot to download mode, but isn't recognized by computer. The basic troubleshooting steps haven't worked.
Click to expand...
Click to collapse
Had a similar experience myself. I also tried using the Verizon update/repair assistant for another device and it did not work. I ultimately ended up borrowing a Note 4, installing the upgrade/repair assitant from that phone onto my pc (enable USB autoplay, then choose to install the software that runs when you connect the phone). The software installed from another Note4 was able to repair my phone without issue.
Tepidlake said:
Had a similar experience myself. I also tried using the Verizon update/repair assistant for another device and it did not work. I ultimately ended up borrowing a Note 4, installing the upgrade/repair assitant from that phone onto my pc (enable USB autoplay, then choose to install the software that runs when you connect the phone). The software installed from another Note4 was able to repair my phone without issue.
Click to expand...
Click to collapse
Interesting. Was your computer unable to recognize the phone as well? How did you borrow another Note 4? I have scoured the internet and haven't been able to find the software online. Would you be able to PM it to me? I would greatly appreciate it as I do not have immediate access to another Note.
ODIN can be finicky with USB cables and ports. Try switching cables and make sure that you're on a USB port that comes straight from the PC and not a hub.
Try uninstalling the Samsung USB driver, reboot the computer then reinstall.
I'm not sure why you were using S5 software when Note 4 is so readily available. I'm not sure that I can recommend using the Marshmallow firmware yet in ODIN. I would use the 5.1.1 version and do the full firmware flash.
what i've done.
Hello Urban415, earlier today my phone decided to take a dump as well gave me that same message with the yellow triangle, i had flashed a bad image (file name : N910VVRU2BPA1_StockRestore.tar.md5) which then gave me that problem.
//-=-=
I went onto Sam Mobile's site, created an account(its free! to download the firmware, it's needed.)
I had to download N910VVRU2BOG5 - 5.0.1 (it took me 2 hours to DL off their site :\ due to free account... but whatevs)
In order to bring my phone back to life also the version of Odin i used was 3.10.6..
My phone was rooted as well and was using N910VVRU2BPA1 - 5.1.1
//-=-=
Hope this helps ! My note 4 Model # : Sm-n910v, bought refurb off ebay.
P.S. Excuse my grammar, punctuation, etc, etc. Also! running Windows 7 x64 and Verizon's assistant didn't work for me either. not even on my windows 8.1 laptop =x!
douger1957 said:
ODIN can be finicky with USB cables and ports. Try switching cables and make sure that you're on a USB port that comes straight from the PC and not a hub.
Try uninstalling the Samsung USB driver, reboot the computer then reinstall.
I'm not sure why you were using S5 software when Note 4 is so readily available. I'm not sure that I can recommend using the Marshmallow firmware yet in ODIN. I would use the 5.1.1 version and do the full firmware flash.
Click to expand...
Click to collapse
I have tried with 2 cords, and am not using a hub. I also already uninstalled, rebooted and installed. Anything else?
The S5 software is only the verizon restore assistant because that is the only samsung software I had available to me. I am not using the firmware for that phone on my note. I tried to do the full 5.1.1 firmware flash, but can only do that when my computer recognizes the device.
SolFox84 said:
Hello Urban415, earlier today my phone decided to take a dump as well gave me that same message with the yellow triangle, i had flashed a bad image (file name : N910VVRU2BPA1_StockRestore.tar.md5) which then gave me that problem.
//-=-=
I went onto Sam Mobile's site, created an account(its free! to download the firmware, it's needed.)
I had to download N910VVRU2BOG5 - 5.0.1 (it took me 2 hours to DL off their site :\ due to free account... but whatevs)
In order to bring my phone back to life also the version of Odin i used was 3.10.6..
My phone was rooted as well and was using N910VVRU2BPA1 - 5.1.1
//-=-=
Hope this helps ! My note 4 Model # : Sm-n910v, bought refurb off ebay.
P.S. Excuse my grammar, punctuation, etc, etc. Also! running Windows 7 x64 and Verizon's assistant didn't work for me either. not even on my windows 8.1 laptop =x!
Click to expand...
Click to collapse
Glad that you got your device to work. Thanks for the information about the Verizon assistant software. Guess it's not just me.
My problem isn't the firmware and finding it online. My problem is that my computer now refuses to recognize the phone as a usb device. I have tried the usual recommended troubleshooting steps to no avail. Did you have this problem?
I'm reaching about as far as I can go, but: did you try to do a factory reset in recovery? I had that work in freeing up a connection issue in ADB once.
@Urban415 I was googling and found one guy who had a similar issue as you... It was for an older device. But what he did was uninstalled the assistant. Then plugged in his phone and reinstalled the software and it installed the correct drivers... Also I'm not to android savvy, but just a thought. If your using the s5 assistant wouldn't it have to download a note 4 image for it to recognize it. Maybe that's why it's not working. Because it doesn't have the note 4 drivers and image??? Just a thought
Sent from my SM-N920V using Tapatalk
Just saying this on top of my head but I have seen system images for the system itself and another with the firmware included. Maybe try the one with the firmware included?
Sent from my SM-N910V using Tapatalk
Urban415 said:
Interesting. Was your computer unable to recognize the phone as well? How did you borrow another Note 4? I have scoured the internet and haven't been able to find the software online. Would you be able to PM it to me? I would greatly appreciate it as I do not have immediate access to another Note.
Click to expand...
Click to collapse
Hey, sorry it took so long to get back.
As I recall my phone was not visible to ADB or Kies while it was displaying the Verizon Repair Assistant screen erreor screen. I suspect that in that state, only the Repair Assistant is able to talk to the phone.
I ended up waiting for my wife to get home (she has the same phone as me) and borrowing her phone to install the assistant software. The software recognized my phone, though it took a minute or two, even though Kies couldn't see it. The assistant downloaded the firmware and flashed it. Phone good as new.
Urban415 said:
I have tried with 2 cords, and am not using a hub. I also already uninstalled, rebooted and installed. Anything else?
The S5 software is only the verizon restore assistant because that is the only samsung software I had available to me. I am not using the firmware for that phone on my note. I tried to do the full 5.1.1 firmware flash, but can only do that when my computer recognizes the device.
Glad that you got your device to work. Thanks for the information about the Verizon assistant software. Guess it's not just me.
My problem isn't the firmware and finding it online. My problem is that my computer now refuses to recognize the phone as a usb device. I have tried the usual recommended troubleshooting steps to no avail. Did you have this problem?
Click to expand...
Click to collapse
similar thing happened to me but on my 2013 nexus 7. I had to download and use "Minimal ADB and Fastboot" and manually (using Commands within windows command-line-interface) restore my device while it was in "fastboot mode". prior to that tried using "WUGsNexus Root ToolKit " which help instruct the user; with screenshots on how to uninstall drivers that might conflict with one another with the use of another program named "USBDeview". that didn't work for me unfortunately . but for i cannot for sure say if its a "Maybe my windows need a refresh/clean slate" or I missed a step.
Thank you to everyone that helped me in this thread. After trying several new cables, uninstalling and re-installing drivers, rebooting, and playing around with software compatibility software, my problem has been solved.
I have now reflashing stock firmware, rooted, and backed up the phone. Cheers!