Ok, I have flashed my Wimo phones more times then I can count.
New to Andriod and I have not been able to get Fastboot to work.
I boot phone to bootloader and select fastboot wait about 10 sec and plug phone into my comp and it never shows fastboot. I have tryed this more then a few times with no luck.
I have read so much in here and on modoco, but I guess I am missing something.
All I want to do is flash to 2.1
Streak (ATT on stock 1.6)
Thank you for you help.
Gary
Why don't you just download the package and mount it to the sd and update? That's what I did.
I keep checking for the update.
but it saying my device is up to date.
Download it from Modaco. It says it's just for custom recovery or O2 Streaks, but it works with AT&T too.
http://www.streaksmart.com/
well, down loaded that pkg. put on my sd card renamed update.pkg
startes to load the stops and gives me a error
FOTA mismatch and reboots.
Well I did have the beta leak of 2.1 already on. You could try downloading that one and trying to flash (6941) What about fastboot though.... after you take the battery out and put it back in, power on holding camera, choose fastboot wait 10 secs and then are you double clicking the fastboot battery file?
Well still a no go for me.
I think this thing will just sit untill Dell gives me 2.2..
its just doesnt stand up to my HD2.
Oh well Andriod so far has not impressed me at all.
Thank you for your help.
Gary
Hey, don't go blaming Android. This is my first Android phone in there is a lot to learn. I was a winmo guy too and it's not like I just picked that up in a second. Many people have succeeded in doing what you are attempting....and they have written about it. Go back and read until you get it right, or maybe it's not for you.
Oh, I am not blaming Andriod.
It must be me not grasping something.
Just have been working on it all day and have not got anywhere with it.
Its your drivers. What os are you using?
Sent from my Dell Streak using XDA App
I am on windows XP.
Find any of the gazillion instructions that tell you how to manually update the correct drivers. .
Blame windowsnot android. ...
You need the correct drivers, from the sound of things.
I Have the same issue.... and YES I have read all the instructions and guides. Even updating the drivers manually from about 6 different sources including the SDK itself and I still cannot get the drivers to install. I had this problem before with my Desire but it was easily fixed with the Drivers update, but not now....
I had the same problem with the drivers, I was unable to do anything until I read where someone said "install the Dell PC Suite" which is located on the SD card. Once I did that everything worked.
I have tryed with Dell pc suite, no go.
then I tryed with Pdanet, no go.
I have read and tryed 3 different ways of doing this and still cant get it.
Have some things I have to do this morning then I will start fresh again and give it a go.
I will hard reset the streak, remove everything I have alreday download on my pc and start new.
I know I am not a idoit, but after yesterday I am starting to wonder.
Install dell PC suite. Connect via fastboot. Wait at least 10 seconds before plugging In the usb. If it still says 'Wait for USB FastBoot detect...', see if Device Manager shows it as 'Android 1.0' and says the driver is not installed. If so, Go into Device Manager, right click the device and choose 'Update Driver Software', then choose 'Browse my computer for driver software', then click 'Let me pick from a list of device drivers on my computer. A list of categories should appear, choose 'all devices' then 'google inc', another list will appear, choose 'Android Bootloader'. The Streak should now show 'FastBoot'.
Sent from my Dell Streak using XDA App
Ok,
starting all over now PC Suite will not work.
I have download PCsuite from the Streak and it will not open get the following error:
I have also downloaded from the dell site and still get this error.
I have done this 4 times now each time restarting the comp and nothing works any ideas?.
C:\Program Files\Dell\PC Suite\Application Laucher\Application Launcher.exe
This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem.
Thank you for any help.
Go to control panel and make sure there are no remnants of the previous dell install.then goto program fils and delete the dell folder. Basically make sure there is nothing left of the previous install. Then try reinstalling.
Sent from my Dell Streak using XDA App
Also at what point do you get this error? Are you trying to run the program? If so you don't need to. You just install it and it gives you the framework to connect. Just install then go through the fastboot procedure.
Sent from my Dell Streak using XDA App
Related
Hey, I've tried various methods of rooting my GSM Hero, and eventually found the method on this site entitled "VillainROM Roots 2.1 RUU for GSM Hero (Confirmed)". I got as far as trying to run runindos.bat, and this just returns the error as explained. If I run "adb devices" I get "List of devices attatched" and then just nothing after it. Strange.
Does it have anything to do with the fact that HTC Sync never picks up my phone?
Windows 7 64-bit
HTC GSM Hero
3 UK
Android 2.1
adb, drivers or usb debugging, check it
Sent from my HTC Hero using Tapatalk
USB Debugging is enabled, not sure how to check adb but what's the correct way to install the drivers? Is it by running the "SDK Manager" program in my SDK folder?
Moved to Q&A as not development.
Get the drivers via the sdk manager, and manually install them via device manager for the device.
Ahh, sorry about the wrong section. I assumed that Development would be things concerning roots.
SDK Manager only seems to let me install "SDK Platform Android X.X", I don't see any driver installations. Also, I'm not sure where it installs these to.
Edit:
Okay I tried to install "USB Driver" but Windows said that it was already up to date. Still not appearing in adb :/.
Hmmm. Search for drivers in dev forum, as I think I posted mine (or instructions to hack them) on one of the Froyd villain threads somewhere.
Also, I presume you have rebooted and tried adb right after reboot
Drivers for you
Thanks to you both, I'll try those later on today.
I'd rebooted both the PC and the phone and tried it. Nothing unfortunately. It just seems to be a big Windows 7 problem.
I use Win 7 without any problems.
Check out this epic guide by BTDAG,...
http://forum.xda-developers.com/showthread.php?t=776056
Good news and bad news. The drivers are now working, adb is working and runindos.bat is doing it's thing. Unfortunately, when it reboots the second time for recovery, there's just a red triangle with an exclamation mark in it.
I rebooted and got back to where I was, but how do I get the "Care Bear" boot screen? Am I supposed to have moved RA-Hero to my phone first or do I not need anything?
Thanks.
Hi Craig. I had to repeat process 4-5 times before it worked so make sure you have your new rom on SD for when it works. I had all same probs but it will get there. As pulser said on villain try changing directory to avoid echo. It seems to load a little more each time.
Sent from my living room.
Hmm, if the recovery thing with the phone in the background comes up, and has "apply:update.zip" as a selection, should I try that? I've tried a few times and that's usually what comes up, along with reboot phone and another couple of selections.
I've got it! Thanks very much for everything. I just kept doing it and it's working now. I got FroydVillain and I'm loving it! I never realized the Hero could be so smooth.
Also sorry for the double post, I'm used to auto-merging on formus.
So apparently no one on here wants to help me unbrick my X10a for free so now I am going to offer money, no specific dollar amount until someone can get it working again, even if it's only for a short period of time. The link to my original thread is linked above, whoever gets it working can request the amount they think it was worth spending their time. Good luck, for both of us. I have seen several others with this same problem, if they would like to join in the bounty for us, and future bricks, feel free to leave a post of PM me.
I only skimmed over your last thread so let me ask a few questions.
Flashtool doesn't work at all?
So what version flashtool do you have and has it worked previously?
Did you unlock your bootloader?
When you connect to flashtool do you keep the back button held the WHOLE time?
EDIT:
Read your thread. Looking at the flashtool screenshot it looks very similar to an error i was having at one point. Even tough i had the drivers installed they didn't want to play nice. I downloaded Flashtool 0.2.9.1 and reinstalled drivers. When in flash mode i seemed to HAVE to hold the back button down the whole time.
I have tried it both ways, to hold it the entire time, or until I get the error, and let go as soon as it starts flashing. Both have the same end result of the aborting of the flash. Also, I've uninstalled and reinstalled the drivers several times as well as used Gordon's reset usb ids everytime I try.
Dacian said:
I have tried it both ways, to hold it the entire time, or until I get the error, and let go as soon as it starts flashing. Both have the same end result of the aborting of the flash. Also, I've uninstalled and reinstalled the drivers several times as well as used Gordon's reset usb ids everytime I try.
Click to expand...
Click to collapse
Are you sure you have a stable connection with your data cable?!! (USB port and cable work fine, not lose or something!!)
Question: The Green Led (the light that comes "on" while you're in flash mode) goes off while you are flashing?
Sorry all, lost my isp for a bit. Yeah, I'm sure about the USB connection. I have gone as far as to taping it down to make sure it doesn't move. lol. And when flashing, the light does stay on but there have been times where the light goes off half way through despite not being moved since it initialized connection.
What where you running?? Did you try seus???
Sent from my Lauda X10a using XDA App
Okay i had your error message too a few times here is what i did i re installed the x10 drivers it was included in flashtool then i flashed stock 2.1 it worked like a charm !
Sent from my X10i using XDA Premium App
Try this:
1- uninstall pcc and seus
2- run some aplication to clean the registry of the computer.
3- install again pcc and seus
4- connect your phone and let PC to install the drivers automatically.
5- use flashtool to flash a firmware designed for you baseband. Try android 2.1 first to test it.
If it still doesn't work try to do all in a computer with another windows version. Sometimes Windows 7 give a little problem to install drivers.
One computer that has never been used for this is excellent because there is no conflicts between applications and drivers
Sent from my X10a using XDA App
Ensure firewall and antivirus disabled on pc .
Kieron
Sent from my X10_AOSP using xda premium
kieronw3 said:
Ensure firewall and antivirus disabled on pc .
Kieron
Sent from my X10_AOSP using xda premium
Click to expand...
Click to collapse
Also turn off UAC (user access control).
Don't know if this will help too but have the latest version of Java installed.
Similar problem
So did your X10 work?
I am having the following problem:
Mistakenly wiped everything using xrecovery, even system.
Now no computer recognizes device (10 different systems with XP, Vista, 7)
unable to boot into flash, stuck at SE logo,
already tried different versions of flashtool, tried all the drivers including gordon gate, android drivers, pcc and seus but device still not recognized
Now is my X10 bricked or what!
Any hope anybody?
phillip.in said:
So did your X10 work?
I am having the following problem:
Mistakenly wiped everything using xrecovery, even system.
Now no computer recognizes device (10 different systems with XP, Vista, 7)
unable to boot into flash, stuck at SE logo,
already tried different versions of flashtool, tried all the drivers including gordon gate, android drivers, pcc and seus but device still not recognized
Now is my X10 bricked or what!
Any hope anybody?
Click to expand...
Click to collapse
Reinstall Windows and then:
1. Download the latest PC Companion from SE site.
2. Install it on your PC then open the programm and choose the "update service" there.
3. Then you'll find there a phrase saying "repair phone".
4. Then only follow the instructions of PC Companion to repair your phone.
And ALWAYS, ALWAYS, ALWAYS read FAQs, Guides, and Tutorials.
Format PC and install SEUS and PC Comp....
Disable UAC in windows 7
Restart PC
Follow procedure for flashing,with Flashtool 0.2.9.1...
Wait for drivers to be installed (must have internet connection)
Use Stock 2.1 Firmware file first!
Run it As Administrator
Change USB Cable, take shorter one and plug in in the back of PC (directly on motherboard)...
I had already tried pcc but I tried again as you said.
Formatted new PC with windows 7, turned UAC off.
Downloaded new pcc and ran the program.
After hitting the update link it says to connect the usb cable but after connecting usb cable it does not install the drivers. It says to disconnect and reconnect if nothing happens for 30 seconds so I did that and upon connecting usb cable it says unable to connect to the phone. I think the phone repair link is after the phone is connected to pcc but I can't connect to pcc.
And how do I connect the usb cable directly to the motherboard? Do you mean to open my desktop cabinet and locate the usb port on the motherboard, disconnect the already connected back and frontpanel usb headers and then connect the usb cable to the usb header on the motherboard?
Also tried flashtool 0.2.9.1 but no success, keeps trying to connect but to no avail.
I tried SEUS awhile ago, it's in the original post. I have uninstalled the drivers and reinstalled them several times as well as uninstalling Windows drivers and only using Gordon's drivers and that did not work. I taped the back button down on the device but that still did not work. I'm at a loss...
About installing the drivers, how about this:
Download the standalone drivers: http://www.megaupload.com/?d=U2PY6QOR and read these instructions provided from SE Support:
First, it is important to install drivers properly.
Start with the SEMC drivers.
When X10 is connected to the computer you should use ADB for X10 not ADB that comes with Googles SDK since it is not compatible with X10, yet. Use ADB for X10 included in attatchment, and write adb devices.
If you get something like CBxxxxxxxx then ADB works with X10. To kill old ADB server you can use adb kill-server command.
Good luck
(Note: i found this info over the net, it's kinda old, May 2010 but may works, who knows!)
Another option to install the drivers is to download and install this software: http://www.mediafire.com/?pq0idzzyasmzui0 This is the Unlock Software provided from cellunlocker.net which i used to unlock my X10, it has the option to install the drivers for you on the software folders (in windows start menu).
Try again after installing these, specially the second option (Unlock Client), who knows, maybe you'll get lucky!
Hope this helps!
How bout this. Start fresh from another PC.
Sent from my Sensation using xda premium
I have updated everything, I have actually started fresh from my Laptop to see if it had something to do with my home PC but it does the same thing. As far as ADB goes, you cannot access ADB if the phone is net set to debugging mode, adb will not recognize the phone, even in flash mode.
Will you can try this it has worked for a few others and if it does work JUST the thanks button is good for me. And just Be Patient go slow and it will get fixed if it's not already. And after you get it working then you can update too what ever Rom you wont.
Have Fun
http://forum.xda-developers.com/showthread.php?p=13163598#post13163598
---------- Post added at 01:41 AM ---------- Previous post was at 01:10 AM ----------
Patricks_book said:
Will you can try this it has worked for a few others and if it does work JUST the thanks button is good for me. And just Be Patient go slow and it will get fixed if it's not already. And after you get it working then you can update too what ever Rom you wont.
Have Fun
http://forum.xda-developers.com/showthread.php?p=13163598#post13163598
Click to expand...
Click to collapse
Also when you've got that fix you can update an root 2.3.3 Stock rom here:
I used Z's way:
http://forum.xda-developers.com/showthread.php?t=1196421
Or you can use Doomlords way:
http://forum.xda-developers.com/showthread.php?t=1196808
Also baba_baba has a real good tread here:
http://forum.xda-developers.com/showthread.php?t=1209749
And please remember too Thank these Developers for their work with the THANKS button
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
littlewierdo said:
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
Click to expand...
Click to collapse
You are the man! Thanks for posting this!
littlewierdo said:
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Click to expand...
Click to collapse
Didn't work. I get caught in an endless loop where it keeps asking me to uninstall the previous version.
What do you mean "edit the KiesVersion.txt"?
bigmout said:
Didn't work. I get caught in an endless loop where it keeps asking me to uninstall the previous version.
What do you mean "edit the KiesVersion.txt"?
Click to expand...
Click to collapse
Ok, what you need to do is copy and paste the download link into a new tab in your browser. This should automatically give you a download dialog box (no need to browse a website). Download the app, its 90 megabytes and when it is done downloading, run it. Follow the on screen prompts.
This DOES work, I know, I did it on three different machines, all running Vista, XP, and Win7.
Alternatively, you can browse to where Kies is installed (C:\Program Files\SAMSUNG\Kies) and look for a file called KiesVersion.txt. Open this in Notepad and you will see one line at the top. Copy and paste the version number REPLACING whatever version is showing:
2.3.2.12064_9
(So you should have just one line showing the version number above).
Save and exit.
Note, if you choose the KiesVersion.txt method, Kies will not update correctly which is why I strongly recommend doing the first method first.
littlewierdo said:
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
Click to expand...
Click to collapse
Thanks man. Your method worked for me!:good:
littlewierdo said:
Ok, what you need to do is copy and paste the download link into a new tab in your browser. This should automatically give you a download dialog box (no need to browse a website). Download the app, its 90 megabytes and when it is done downloading, run it. Follow the on screen prompts.
Click to expand...
Click to collapse
Yeah, I did all that. I downloaded the installer and clicked on it. It started installing, then asked me if I wanted to uninstall the old version of Kies. I said yes, and it started uninstalling.
And... that's as far as I can get. After that, it loops back and keeps asking me if I want to uninstall the old version of Kies.
littlewierdo said:
Alternatively, you can browse to where Kies is installed (C:\Program Files\SAMSUNG\Kies) and look for a file called KiesVersion.txt. Open this in Notepad and you will see one line at the top. Copy and paste the version number REPLACING whatever version is showing:
2.3.2.12064_9
(So you should have just one line showing the version number above).
Save and exit.
Note, if you choose the KiesVersion.txt method, Kies will not update correctly which is why I strongly recommend doing the first method first.
Click to expand...
Click to collapse
I'll try this -- thanks.
bigmout said:
Yeah, I did all that. I downloaded the installer and clicked on it. It started installing, then asked me if I wanted to uninstall the old version of Kies. I said yes, and it started uninstalling.
And... that's as far as I can get. After that, it loops back and keeps asking me if I want to uninstall the old version of Kies.
I'll try this -- thanks.
Click to expand...
Click to collapse
Maybe try uninstalling the version you have before you install the one I posted. Might be a version problem (my version that I had installed might be newer/older than yours).
Thx...i finally got it working
Sent from my SAMSUNG-SGH-I717 using xda premium
FINALLY!!!!!! Thank you so much! Downloading the newest version you posted finally got rid of the infinite updating issue plaguing me.
BTW I uninstalled the old version first before installing the new one since im seeing issues with replacing also
Sent from my Galaxy Nexus using Tapatalk 2
29% about 40 mins way to slow to download.
Edit: Received a timeout error damn!!!!!!!
Sent from my SAMSUNG-SGH-I717 using xda premium
Thank you for the debugging tip! This worked when I used it regularly. However, as soon as I went into download mode, it started the infinite connecting again! Any idea what is up with that?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
My phone still won't connect
Sent from my SAMSUNG-SGH-I717 using xda premium
whittakerh said:
Thank you for the debugging tip! This worked when I used it regularly. However, as soon as I went into download mode, it started the infinite connecting again! Any idea what is up with that?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
It has to do with the bizarre way Windows handles drivers.
EVERY phone state has to have a different 'driver' installed, although technically, it is using the same driver for each phone state..
The Note actually has five states, Download mode (this is the mode you would put your phone into to 'Odin' anything to it), Recovery mode (Clockwork recovery menu), Debugging mode (turn on USB Debugging) - also known as ADB mode, Mass Storage, and Wifi Direct (useful for connecting to your PC's files or public files on your phone using your PC - requires the PC to have wireless capability). Due to the way plug and play works, any device connected to your PC must put out a 'ping' to tell the OS what it is (a device name). Samsung has opted to really confuse everything by reporting a different device name for all these different states rather than doing what most devices do, a recovery mode and a mass storage mode (two states instead of the 5 Samsung is using).
Installing the samsung note driver via kies is sufficient to cover all the different states (windows just duplicates the driver for each new state it has not detected previously) but in order to cover every state the phone can possibly be in, you have to plug in the phone while the phone is in that state (ie. plugging it in with USB debugging on will install the drivers for ADB mode). One other note, just in case you are getting the brilliant idea to go ahead and -pre-install all of these different states, it has to be done for each USB port (each state) and Windows tends to remove unused drivers after a short period of time (if you havent put your phone in download mode and plugged in to your PC in awhile, chances are, Windows will have to reinstall the driver for this state again). This is why in the instructions I listed, I explain putting the phone into mass storage mode and then back into ADB mode - this forces windows to install the drivers for each state.
For those still having trouble with this, reboot your PC and try the instructions again. Pay very close attention to the system tray (the icons by your clock in the lower right corner - typically unless you moved your start menu).
MAKE SURE that windows FINISHES installing the driver for mass storage BEFORE you switch to ADB mode or you will have problems. BE PATIENT! Put your phone in mass storage and go get a coffee, do a cross word puzzle, take a shower, whatever. It takes anywhere between 30 seconds to 5 minutes to install the driver and if you interrupt the process, things become wonky until you reboot.
There will be an icon by the clock that is animated while the driver is installing (click it and it will tell you it is installing the driver). When it isnt animated, clicking it will tell you that windows finished installing the driver. DONT RELY ON THE ANIMATION! Click the icon and be sure it has installed.
Also, you cannot have Kies running while Windows is installing the driver. If you do, windows will correctly install the driver but Kies will never detect the phone. It is possible that shutting Kies down and restarting it (and repeating the steps I mentioned to get Kies to connect) may correct the issue but most likely, it will require a reboot and then you will have to run thru the steps I outlined again to get it to connect properly.
This is a combination of Windows and Samsung both. Windows could handle this so much better, Samsung could have reported the device as two possibilities instead of 5. But, what can I say, One company is Korean and one is American and they each like to do things their own way.
Thanks, OP - finally able to get the ICS update. This whole process was a complete cluster****. Samsung should work on that.
Edit: Guess I spoke too soon. Kies was able to recognize my Note and began the update process (i.e., asked me if I wanted to update, had to agree to whatever, etc.), but after it downloads the firmware and begins "preparing firmware upgrade components" to install the upgrade it loses the connection with the phone and restarts the whole process again. Kies doesn't say anything about losing the connection - the box that shows the status of the update just closes and Kies doesn't register any connected devices (though it starts the "connecting" process again a few seconds later. Any suggestions?
NickNaylor said:
Thanks, OP - finally able to get the ICS update. This whole process was a complete cluster****. Samsung should work on that.
Edit: Guess I spoke too soon. Kies was able to recognize my Note and began the update process (i.e., asked me if I wanted to update, had to agree to whatever, etc.), but after it downloads the firmware and begins "preparing firmware upgrade components" to install the upgrade it loses the connection with the phone and restarts the whole process again. Kies doesn't say anything about losing the connection - the box that shows the status of the update just closes and Kies doesn't register any connected devices (though it starts the "connecting" process again a few seconds later. Any suggestions?
Click to expand...
Click to collapse
Use the link I provided in the original post to download the updated version and stick it in a folder you can find.
Completely UNINSTALL Kies.
Unplug your Note from the PC.
Reboot your PC.
Reinstall Kies using the new version you downloaded.
After installing, reboot your PC.
After your PC has rebooted, go through the process of installing the Note drivers as I described in the original post (see below). Once you reach the step of putting the phone in USB debugging mode and have plugged it into your PC, wait until AFTER Windows has told you the drivers have been correctly installed. If Windows gives you an error that the drivers did NOT install correctly, reboot and try again. You need to pay attention to the icon in the system tray, click on it to see whether it is currently installing, whether it successfully installed, or whether it failed if you arent seeing the icon animation.
MAKE SURE to watch the icon near the clock, do NOT change the USB mode on the phone until AFTER windows has told you it has installed the driver for that mode.
AFTER you have enabled USB Debugging and plugged it into your PC, wait until AFTER Windows says that it successfully installed the driver, then, WITHOUT unplugging your phone, launch Kies and proceed to update your phone.
littlewierdo said:
Use the link I provided in the original post to download the updated version and stick it in a folder you can find.
Completely UNINSTALL Kies.
Unplug your Note from the PC.
Reboot your PC.
Reinstall Kies using the new version you downloaded.
Click to expand...
Click to collapse
Thanks for all of these suggestions. This makes complete sense but I'm still having a problem (Windows Vista 64):
- I uninstalled using Kies Uninstall tool
- I searched out and deleted all other Kies related files, including program data stored under the user profile
- I rebooted my PC
But... when I try to install Kies from the new .exe file, it goes back to the loop: uninstall / install / uninstall.
Is there something more that needs to be done to "uninstall Kies" completely? e.g. modify a registry?
PS about the "loop" it goes like this:
10 Pop up: Before you install the new version, you need to uninstall the old version of Kies
20 Me: OK
30 (it then uninstalls - allegedly)
40 Pop up: You will now install the new version.
50 Me: OK
60 goto 10
UPDATE (7/17):
I used a registry cleaning utility to wipe out Kies related keys in the registry. I was then able to install the new, downloaded version of Kies and successfully updated my phone. So... I assume the loop was caused by Kies not being able to properly uninstall itself. (Or... it could have just been me...)
There is a possibility of user account control getting in the way. Forgot to mention that before you run the installer, you need to right click on the exe and select the compatibility tab and then select 'run this program as administrator'. For whatever reason, some machines I have noticed that Windows doesnt always automatically detect when a program needs to be run as admin and it needs to in order to access everything it needs to.
Why arent people flashing ICS the way everyone else has been for months? Seems like its causing more problems than anything
Sent from my SAMSUNG-SGH-I717 using xda premium
Newer Version of Kies!
littlewierdo said:
Alrighty, two problems I ran into trying to get ICS up and running.
Problem number one is what I call the infinite Kies update loop where Kies will ask you to update, you do all the steps, and Kies AGAIN asks you to update to the same version you just supposedly did. The software has to be current in order for Kies to perform the update. Now, there are two ways to go about it:
You can either edit the KiesVersion.txt and just type in the current version to 'fake' Kies out
OR you can download the latest build HERE:
downloadcenter.samsung.com/content/SW/201110/20111024092325174/Kies_2.3.2.12064_9_7.exe
Doesnt matter if you have another version installed or not, the installer will guide you through the process and uninstall the previous version. Takes about 5 minutes to install the whole deal.
Problem number two is getting Kies to actually recognize your device instead of just 'connecting' forever.
The way to get around this is the following:
Shut down Kies
Unplug your phone, then ON YOUR PHONE, go to settings>Wireless and Network>USB Settings and enable mass storage (Ill fix the wording on this shortly as my phone is currently updating but its only one option). After doing so, it will tell you that USB Debugging needs to be disabled (I think it will do this automatically), hit the Continue box and then plug your phone in. YOU DO NOT need to tap the Connect phone button under the little Android guy that appears on your phone screen. Now, let Windows install the driver.
NOW, unplug your phone and go to Settings>Applications> and enable USB Debugging (its the last option in the applications menu) and let windows install the driver.
Now, launch Kies and it should only take about 30 seconds to connect.
Note that your phone MUST be in USB Debugging for Kies to upgrade the firmware (which is why the last thing we did was enable USB Debugging, your phone will already be in USB Debugging mode).
Hope this helps
Click to expand...
Click to collapse
This worked great to finally upgrade my Kies to Version 9.7, however there is a newer version 2.3.2.12064.10 available so when trying to update it once again goes into the loop. Any idea as to where to find this newer version?
Cubbump1 said:
This worked great to finally upgrade my Kies to Version 9.7, however there is a newer version 2.3.2.12064.10 available so when trying to update it once again goes into the loop. Any idea as to where to find this newer version?
Click to expand...
Click to collapse
I found this direct link at the German Samung website: downloadcenter.samsung.com/content/SW/201105/20110512115717796/Kies_2.3.2.12064_10_1.exe (Grrr...I am not allowed to post a working link since I am a new user. Sorry for that.).
Worked for me, but I had to remove the old version on my own before installing the latest version with this installer. Otherwise it got stuck in the infinite uninstall loop.
THE PROBLEM HAS BEEN SOLVED!
If you have the MTP usb device driver error (code 10), then scroll down and try what worked for me.
Sparrow245 said:
So, I used Odin to reset my vibrant back to stock 2.1. I then tried to get it to 2.2 using Samsung Kies, but when ever I try to use it, MTP Device fails to install. Anyone know how to get the driver to install / work correctly so that I can use Kies? Thank you in advance.
Click to expand...
Click to collapse
You should really avoid using kies if possible. It is notorious for hard bricking phones, meaning they become paper weights if something goes wrong. You should install clockwork mod recovery and install a custom 2.2 ROM, there are literally tons to choose from and they are pre-rooted. Some of the custom ROMs have odin images so you could actually skip the clockwork recovery step. I'll link you to the 2.2 ROM I'm using or you can search for something different. Here is Axura 2.2, use the odin image in the 3rd post http://forum.xda-developers.com/showthread.php?t=1787267.
EDIT- if you also need drivers for your phone then go here http://forum.xda-developers.com/showthread.php?t=728929
Sent from my SGH-T959 using Tapatalk
If you want 2.2 (Froyo) installed on your Vibrant, like the other poster said, there are literally tons of great builds.
Here is a link to one that I really liked, it had great battery life, and overall good performance. Bionix V - http://forum.xda-developers.com/showthread.php?p=21324042
As stated above, please avoid using the Kies software, it generally creates many more problems than it is worth.
I've used Kies many times, so I know what I'm doing. But apparently this time something about the MTP driver isn't going alright. Could be that I have this fairly new computer? I've already tried installing the vibrant drivers, but for what ever reason I keep getting a code 10 error for the MTP usb device. :/
Well if your not doing so already, try running the program as administrator.
However, not sure why you are so hell bent on running the stock Froyo via Kies, when there are so many other amazing Froyo/GB/ICS/and now JB custom ROMs that work MUCH much better, and have way better support than Samsung could ever provide.
However, to each his own. Good luck to you with your endeavors!
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
I know the thread is for a tablet, not sure which version of windows your running, but maybe something lime this is what you are looking for: http://forum.xda-developers.com/showthread.php?t=1150211
Sparrow245 said:
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
Click to expand...
Click to collapse
Google code 10 error mtp
You should find a link that says fixed code 10 mtp error Samsung galaxy
It is a post on android forums or phandroid??? You should see it and it should fix your error.
sent from my magic box to yours
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Sparrow245 said:
I've used Kies many times, so I know what I'm doing.
Click to expand...
Click to collapse
When kies hard bricks your phone I'll be here to say I told ya so. Its really an unnecessary risk but its your phone, good luck.
Sent from my SGH-T959 using Tapatalk
@sparrow, that's exactly what I read but it was to much to type.
sent from my magic box to yours
Please Help
hey man did you ever get the MTP driver to start? I am still at a loss with this myself.
Sparrow245 said:
Which ROM I want has nothing to do with my question. The problem is the MTP usb device, which apparently fails to start. (Code 10)? I've seen that it's a common problem, but there isn't any one definite answer. I was hoping maybe someone here knows how to fix it?
Click to expand...
Click to collapse
Sparrow245 said:
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Click to expand...
Click to collapse
This is the steps used to fix.
Sent from my SCH-I535 using xda premium
Now is really solved.
For some reason, any of those options helped me to make it work:
- Reinstall Windows Media Player
- Remove registry key
- Clean up old usb drivers
- re-install 100 times drivers from Verizon, Samsung. Even old versions.
- Install from Windows Update. I tried to do that 1000 times. Gosh!
- enable UMT access (mass storage) on the phone.
The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.
Windows 7 x64
Attached the files. Go to the devices manager and update the drivers.
Israel Leite
Sparrow245 said:
Ah! Finally found a solution! Not sure if this will work for everyone, but it worked for me.
1. Plug up your phone like usual. Connect with Samsung Kies. Obviously, you will get get MTP code 10 error.
2. Go to the device manager, and then uninstall the driver. Unplug your phone.
3. Go to c:\windows\system32\drivers and rename wudfrd.sys and winusb.sys to wudfrd1.sys and winusb1.sys respectively.
3. Plug your phone back in, and connect with Kies.
4. The computer will try and install the driver again, but fail.
5. Go to the device manager again, and attempt to update the driver. It should fail, and you should get a (code 28) error this time. Make sure you have a code 28 error!
6. Go back to c:\windows\system32\driver and rename the 2 files back to it's original names.
7. Go to c:\windows\inf and look for a file named wpdmtp.PNF. Take the file, and move it somewhere else (like your desktop) don't delete it.
8. Now go to the MTP usb device again, and attempt to update drivers. It should update, and recognize your device now.
This is what worked for me, I don't know if it will work for you. I'm not responsible for anything that goes wrong.
Click to expand...
Click to collapse
Thanks a ton...saved my day.
I have searched (I have 12 tabs open as I type) these forums. I see a few similar cases but I am not finding a solution. I have use CMHENDRA's guides but I am having no luck. (It is my daughters phone so I will give you what information I know) BTW, I contribute in the Note II galleries, I have rooted and flashed HTC One X, Several Nexus 7's, my Note II, Galaxy SII, Galaxy S, HTC Sensations, Nexus 4 and a few older ones. I can currently see all those phones on my laptop. Not the L9.
I believe my son tried to flash CWM for my daughter. She is notoriously rough on phones and he was trying to make sure she was protected. The phone boots into the LG Security Error screen. I can get it to boot into S/W Upgrade mode. I have completed or can complete all the steps to most of the guide. I CANNOT get my Win8.1 laptop or my sons Win7 laptop to recognize the phone to complete any of the guides. B2C, Fastboot, etc. I can see various entries in the Device Manager, I uninstall and reinstall with Driver Signing turned off. I have now reached the point where I have done so many things that I have probably confused myself.
When it did get the security error, the software had been set to USB Debugging and Unknown Sources was allowed. The firmware was 20H. B2C cannot get the phone information (I know it is probably the drivers as is everything else).
Any help, ideas, etc. would be great. I would love to be a hero for my daughter.
dsore1218 said:
I have searched (I have 12 tabs open as I type) these forums. I see a few similar cases but I am not finding a solution. I have use CMHENDRA's guides but I am having no luck. (It is my daughters phone so I will give you what information I know) BTW, I contribute in the Note II galleries, I have rooted and flashed HTC One X, Several Nexus 7's, my Note II, Galaxy SII, Galaxy S, HTC Sensations, Nexus 4 and a few older ones. I can currently see all those phones on my laptop. Not the L9.
I believe my son tried to flash CWM for my daughter. She is notoriously rough on phones and he was trying to make sure she was protected. The phone boots into the LG Security Error screen. I can get it to boot into S/W Upgrade mode. I have completed or can complete all the steps to most of the guide. I CANNOT get my Win8.1 laptop or my sons Win7 laptop to recognize the phone to complete any of the guides. B2C, Fastboot, etc. I can see various entries in the Device Manager, I uninstall and reinstall with Driver Signing turned off. I have now reached the point where I have done so many things that I have probably confused myself.
When it did get the security error, the software had been set to USB Debugging and Unknown Sources was allowed. The firmware was 20H. B2C cannot get the phone information (I know it is probably the drivers as is everything else).
Any help, ideas, etc. would be great. I would love to be a hero for my daughter.
Click to expand...
Click to collapse
I can't get mine to work either. Closest thing I've gotten is using omap4boot-for_optimus-v1.21
its different from some of the others, in that its a blue background and it doesnt actually list the p769. However, after selecting option 5, and following onscreen instructions, I was able to get my front capacitive buttons to light up, but nothing else. I can't enter S/W upgrade mode, I can't get LG recovery tool to recognise my phone, I am absolutely **** out of luck. I dont know if using omap4boot-for_optimus-v1.21 will help or hurt you, but im just explaining my experiences.
Have you installed the omap driver for fastboot?
Thanks for your replies. Windows 8.1 is installing the OMAP driver and when I try to update it, Windows says it has determined that I have the best one installed already or some BS like that. That seems to be the last piece of the puzzle. I am not getting it to use the fastboot commands and when I am in the LG upgrade thing, it cannot connect on the first of the three calls so it says to check the USB cord and connection. ( I have tried 5-6 cords including the OEM cord ).
Thanks again for your help. I will uninstall the OMAP drivers when I get home and see if I can't get the ones I downloaded to install.
I don't have Windows 8.1 so I'm not sure how to address the driver issue. I reer as wel.commend you uninstall the driver, both of them. The one under Android Phone in the device manager and the one called TI Boards in the device manager.
1. Uninstall all OMAP drives (Two of them)
2. Disconnect from the internet (to preventing Windows update from selecting its own driver.
3. Follow steps to fastboot. When connecting your phone have device manager open and right click the device that is flashing on and off (you will see the device manager refreshing and stuffs. It will dissappear after about two seconds but if you get the right click in and the option to install the driver, do it, point to the fastboot driver.
4. Disconnect phone after driver install and pull the battery.
5. Fastboot again, using option 1.
6. Quickly install same driver on the new device in device manager. Be quick.
7. Disconnect, Pull battery
8. Fastboot again
9. Flash ICS U and X
10. Make sure your LG drivers are installed.
11. Reboot PC.
12. Now you should be able to get into SW UPGRADE MODE with the plugging in of the USB
Should not lock up at 15%, make sure you have drivers installed for this.
13. Should work and reboot to home screen automatically.
14. If you really must, fastboot again and install JB U and X
dsore1218 said:
Thanks for your replies. Windows 8.1 is installing the OMAP driver and when I try to update it, Windows says it has determined that I have the best one installed already or some BS like that. That seems to be the last piece of the puzzle. I am not getting it to use the fastboot commands and when I am in the LG upgrade thing, it cannot connect on the first of the three calls so it says to check the USB cord and connection. ( I have tried 5-6 cords including the OEM cord ).
Thanks again for your help. I will uninstall the OMAP drivers when I get home and see if I can't get the ones I downloaded to install.
Click to expand...
Click to collapse
I've heard fastboot (and several other programs) aren't working on Windows 8. You need windows 7
Sent from my LGMS769 using XDA Premium 4 mobile app