hi ,
After several attempts ...finally managed to install kies software in my laptop. But while trying to open it i am getting a popup message box throwing an exception and kies is throwing up some fatal error exception..
I have Vista with 32 bits
Installed .net 3.5,windows mobile device center,directx9.0
Not sure what I am doing wrong..Any help would be greatly appreciated.TIA.
Related
Hi,
I keep getting error (Code 43) when trying to upgrade my O2 2002 ROM to WM2003SE.
I've tried everything to get around the error, the only thing i haven't changed yet is the bootloader version. (Currently on v 5.22)
If anyone can provide some advice this would be great.
Thanks
W
Bootloader 5.22 is alright. Have it also and do not have any Problems with it.....
Have you tried another PC to do the upgrade?
Stefan
Hi Stefan,
Yeah - I have tried other machines to do the upgrade - 2 laptops and a desktop.
All report the same error.
The wierd thing for me is that it seems to be Windows XP that reports the error - I get a Code 43 error in device manager - I've attached an image of the error i get.
I've also upgraded all my laptops USB drivers, chipset, BIOS - basically everything to see if it was a problem with a version of the driver or firmware i was running but the error remains unchanged.
Everything runs just fine until Programme A wants to upload the new image - the screen where you should see the progress bar as the new ROM is uploaded - I see that screen for a split second before the Qtek reboots back into the old ROM!
Thanks for the reply
W
Code 43
Windows has stopped this device because it has reported problems. (Code 43)
You could try a different usb port and also make sure it is connected direct and not through a hub.
Yup!
Tried both my USB ports, also tried disabling the "USB Root Hub" in Device manager - I don't have a USB hub plugged into my laptop, but there is one reported in Device Manager - I guess it's internal to the PC?
I figured that if there was a hub built into the laptop that would cause the communication problems experienced by USB hubs.
I couldn't disable all the USB Root Hub instances without switching off the USB port, so i closed all the ones i could and still have the port alive.
Still got the problem - The USB Root Hub in Device Manager - you think this is the "Hub" that the upgrade documentation says will create the error?
I give up...
Thats it! Back to the Good ol T-Mobile v4 ROM.
I've done everything including downgrade my laptop to Win 98 to try USB 1 drivers for this WM 2003 SE upgrade.
I've read every research article, installed every patch, been through TechNet and MSDN libraries.
This thing will just not work!
The universe is trying to tell me something!!
usb and 98 is not the best match
some chipset require special drivers for usb to behave like via
with xp having the latest service pack is prob a good idear
I am having problem running kies as it keep crashing at start up with dialog box showing the message ' mainstage has stopped working' reinstalling kies didn't help. Anyone had this problem?
Ps: I tried searching function from the xda app and it return no result before posting here.
Sent from my GT-I9000 using XDA App
Flash JM2 problem gone away
kcharng said:
I am having problem running kies as it keep crashing at start up with dialog box showing the message ' mainstage has stopped working' reinstalling kies didn't help. Anyone had this problem?
Ps: I tried searching function from the xda app and it return no result before posting here.
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I had the same problem under Windows 7 64bit. Solved it by installing Windows Mobile Device Center, don't ask me why :-(
Thank you for replies. I have tried to reinstall MDC but that doesn't seemed to help solve the problem...
Still cannot use Kies.. sigh..
Solved
Kies require Windows Mobile Device Center on newer Windows, activesync on older Windows.
--------------------------------------------------------------------------------------------------
WAS:
I have just purchased Galaxy S.
Installed Kies on windows 7 64 bit, kies doesn't start/work at all. It remain at splash screen. When open task manager I found the splash process and form1.
It is a big delusion
Samsung make software only for 32bit?? How to sync 232 contacts from iphone without outlook??
Samsung, sigh ..
Regards
Thanks for the hints everyone.
My 'mainstage' problem seemed to have been solve with reinstallation of the latest Kies from samsung which I have just downloaded. That being said, kies open and run fine, but I am back to the same old problem unable to connecting my phone to kies. This software is really a POS.
My system is Window 7 64Bit home professional.
Also just to note, I notice that kies requires .net framework for window xp and vista. To be safe.. and it might be totally unrelated... I enabled the Microsoft .NET framework 3.5.1 on window 7 when I reinstalled the new version of kies.
Yes, and do not forget Windows Mobile Device Center on newer Windows, activesync on older Windows.
Regards
Thanks
Last note really.
Today the in a last ditch efforts to connect Kies due to upgrade from JF4 to JG4 over kies, I have finally decided to format my internal SDcard.
Kies was able to connect to my phone after several reboot attempt of my computer and telephone. Upgrading to JG4 seemed to have no problem connecting to Kies so far. However, I have my doubt that after installing several programs the problem will probably pop back up again.
Cheers Everyone
cyberz said:
Yes, and do not forget Windows Mobile Device Center on newer Windows, activesync on older Windows.
Regards
Click to expand...
Click to collapse
Kies Mainstage Still Not Working
I have tried uninstalling, reinstalling and using different versions and Kies Mainstage still does not allow Kies to start up.
I've installed Mobile Device Manager and still nothing.
Seems as though Samsung exec's opted for a slick, pretty GUI without consideration to actual functionality!
At this rate, I will never be able to upgrade to froyo 2.2 unless someone writes an install package that works.
frustrated.
Galaxy S, 2.1 update 1 Eclaire. 2 Gb Micro SD card.
Laptop: Asus 3 Ghz blah, blah, blah
kingconnought said:
I have tried uninstalling, reinstalling and using different versions and Kies Mainstage still does not allow Kies to start up.
I've installed Mobile Device Manager and still nothing.
Seems as though Samsung exec's opted for a slick, pretty GUI without consideration to actual functionality!
At this rate, I will never be able to upgrade to froyo 2.2 unless someone writes an install package that works.
frustrated.
Galaxy S, 2.1 update 1 Eclaire. 2 Gb Micro SD card.
Laptop: Asus 3 Ghz blah, blah, blah
Click to expand...
Click to collapse
Same for me....the strange thing is that some weeks ago it worked....i use windows 7 64 bit
Kies Mainstage Still Not Working
kingconnought said:
I have tried uninstalling, reinstalling and using different versions and Kies Mainstage still does not allow Kies to start up.
I've installed Mobile Device Manager and still nothing.
Seems as though Samsung exec's opted for a slick, pretty GUI without consideration to actual functionality!
At this rate, I will never be able to upgrade to froyo 2.2 unless someone writes an install package that works.
frustrated.
Galaxy S, 2.1 update 1 Eclaire. 2 Gb Micro SD card.
Laptop: Asus 3 Ghz blah, blah, blah
Click to expand...
Click to collapse
I had similar problems running Kies on Win 7 x64. What I did was do a fresh install of the updated Kies version 103_100_2 (from Samsung UK site), ie. uninstall old Kies and remove any lingering directories first. Then Uninstall the Samsung USB drivers installed with Kies. Then install the x64 bit drivers for Samsung mobile devices. Worked a treat.
You can get the x64 bit drivers from Softpedia website
cheers
Having the same problem. It's infuriating.
Kies was working fine until about a month ago and now I cannot open it. Have followed the advice given in this thread but no luck in getting it to start.
Running Windows Vista 32 Bit
mainstage not working
I have vista 32bit
I reinstalled the latest version of kies it still didn't work so I then installed .NET framework 4 and that seems to have solved the problem.
hope this helps for all you vista 32 bit operators that have the mainstage problem.
took me two hours to work out but seemed to correct the problem by downloading the 4.0 version of .netframework.
kies seems to be working now
let me no if this helps
jay
Fix for XP:
I had exactly the same problem on my XP Netbook and solved as follows:
Uninstall Kies
Uninstall Samsung Modem for Mobile Phones
Uninstall Microsoft Silverlight
Uninstall Microsoft Silverlight SDK
Reboot
Install Kies
Hope this helps.
A.
PS Reasoning behind this is if you look at the error log file that the crash produces and is about to send to Microsoft then you see that the exception occurred in XamlParse... Xaml is the xml language used by Silverlight and WPF.
PPS Samsung get your act together and write software that works properly.
PPPS Samsung give us a way to update your phones without having to use the piece of cr*p you call Kies.
I'm new at this, but I've successfully downloaded Kies(the Samsung PC interface for Galaxy) and installed it. However, it fails to launch. I've downloaded twice and reinstalled, but still doesn't work.
Error message "The Application failed to initialize properly (0xc0000135). Click on OK to terminate the application"
What's up with that? Anybody can help please?
Think is relies on .net framework is yours installed and upto date?
Curfish said:
Think is relies on .net framework is yours installed and upto date?
Click to expand...
Click to collapse
It needs .net 3.5 installed. I never got it to work on my Windows XP at work, but it works on my windows 7 at home. It's a pain, I seems to have to install the 64bit drivers everytime I need to use.
Oh..how do I get an update of .net framework on my XP? It doesn't prompt for that?
*Facepalm*
Ever heard of windowsupdate.com?
Firmware update
Thanks all...I've managed to install Kies. Now it says there's a firmware my Galaxy needs updating, but as I go down the procedure, it says it cannot update as it needs 1000Mb space...my phone still has 1.6G available..what's happening? In any case, this Kies sucks BIG TIME!!
I have a user who just received a new Samsung Galaxy Note 3. When he tries to plug it into his computer - using a USB3 or USB2 cable - it errors with, "This application has failed to start because Wlanapi.dll was not found. Re-installing the application may fix this problem." The user is running Windows XP x64 sp2 on his desktop.
I've searched around the web finding kb918977, which had the download "WindowsXP-KB918977-v6-x86-ENU.exe". Unfortunately that gives me the old hardware platform error. I've also found some sketchy looking driver download sites, but I'm not much for taking that risk. Is there an XP x64 version of this file somewhere or is my user SOL with his Galaxy Note on that machine?
albion01 said:
I have a user who just received a new Samsung Galaxy Note 3. When he tries to plug it into his computer - using a USB3 or USB2 cable - it errors with, "This application has failed to start because Wlanapi.dll was not found. Re-installing the application may fix this problem." The user is running Windows XP x64 sp2 on his desktop.
I've searched around the web finding kb918977, which had the download "WindowsXP-KB918977-v6-x86-ENU.exe". Unfortunately that gives me the old hardware platform error. I've also found some sketchy looking driver download sites, but I'm not much for taking that risk. Is there an XP x64 version of this file somewhere or is my user SOL with his Galaxy Note on that machine?
Click to expand...
Click to collapse
I'm not sure anyone else will ever have this problem given the age of the OS, but just in case... I was able to get an older version of the Samsung Kies to install. Although Kies 2.5 was not compatible with the Note 3, it did install the driver I needed. Now my user can at least transfer files from his device in Windows Explorer. I downloaded the older version from this site http://www.oldapps.com/samsung_kies.php?system=Windows_XP_x64
-Craig
And by user... what your reallyyyy trying to say is...
Jokes aside thanks it might help someone else with the same error.
Sent from my SM-N900V using Tapatalk
so i was getting lots of request about com port failure regarding my thread on un-bricking, suddenly lots of people want to install stock India rom for kitkat update
so i thought lets put all problems people are facing in one thread
USE only XP 32 bit or win 7 32 bit OS nothing else works.
After installing drivers plug the phone and wait for drivers to install and note the com ports
Prob) gnqc download doesn't works gives error "application failed to start"
sol) install VC++ 2005 redistributeble SP1 ATL security upgrade
Prob) receive incorrect parameter error.
sol) you are using Chinese flash tool so make sure your copy of windows supports Chinese change local settings in control panel or use English version
Prob) error in gnqc bp_image file doesn't exist
sol) make sure your stock rom is Indian version and does not have Chinese characters
Prob) open com port failure
sol) check if your com ports are used by any other app if not it means com port drivers are not installed for your phone all you have to do is to reboot the phone while still plugged in and it will install another set of drivers
will it work with windows 8.1 64 bit running windowx xp sp1 in virtual box
omkargarg said:
will it work with windows 8.1 64 bit running windowx xp sp1 in virtual box
Click to expand...
Click to collapse
No and to everyone trying to do that in virtual box let this be a fair warning the reason is during flashing your phone will switch off/restart that will cause the USB to unplug from virtual machine it will be equivalent to removing USB while flashing and result in bricked phone. though it may work in emergency mode but don't try unless someone who has done it confirms or you have no other option left
PS : if you are on win 8.1 x64 I suggest you to install win7 32 bit on a completely different hard drive because chances are you have an EFI system and your hdd is under gpt so installing 32bit os on that hdd will not be possible
dhirajranger said:
so i was getting lots of request about com port failure regarding my thread on un-bricking, suddenly lots of people want to install stock India rom for kitkat update
so i thought lets put all problems people are facing in one thread
USE only XP 32 bit or win 7 32 bit OS nothing else works.
After installing drivers plug the phone and wait for drivers to install and note the com ports
Prob) gnqc download doesn't works gives error "application failed to start"
sol) install VC++ 2005 redistributeble SP1 ATL security upgrade
Prob) receive incorrect parameter error.
sol) you are using Chinese flash tool so make sure your copy of windows supports Chinese change local settings in control panel or use English version
Prob) error in gnqc bp_image file doesn't exist
sol) make sure your stock rom is Indian version and does not have Chinese characters
Prob) open com port failure
sol) check if your com ports are used by any other app if not it means com port drivers are not installed for your phone all you have to do is to reboot the phone while still plugged in and it will install another set of drivers
Click to expand...
Click to collapse
Plz help I am doing everything you say but my device is shown as "unknown device " still facing the open Com port fails problem.. I installed win 7x32 but still the same. ..
Nevermind I fixed it using the new update
Thanks BTW