System configuration: X10 (R2BA020), Win7 x64 (english), SE PC Suite 2.00.142
Suite installed without any error messages. When I connect the phone via USB, Windows is searching for drivers but can't find one which matches with the device.
I've tried it manually via device manager (Other devices: X10i) and used for the update-driver-wizard the path to the driver folder (program files\SE...\drivers), but no matches...?!?!
I can see two entries with USBDeview:
Vendor ID:0fce
Device ID: 212e and 313e (Debug and no-Debug Mode)
Device class: Smar
Device type: unknown
Description: SEMC Mass storage USB device
The drivers are digitally signed by MS, so what's the problem?
Hi,
I have two small apps that I have devleoped using eclipse and the emulator. Now I want to use eclipse and my htc aria.
I followd the sdk's directions for downloading the usb driver and I now have a folder named "usb_driver" in my sdk. However, windows can't find a driver for the htc aria in that folder.
THe next thing that I tried was to use "HTC sync" from HTC. However, I can't even get HTC sync to work all. MY aria can't find HTC sync on my VIsta compter. After digging into this, I found that windows gets an error when it tries to run the htc sync driver. This is detalied below:
Device Manager:
Android USB Devices: My HTC
Device status: Windows cannot initialize the device driver for this hardware. (Code 37)
Click 'Check for solutions' to send data about this device to Microsoft and to see if there is a solution available.
Description:
Windows was able to successfully install device driver software, but the driver software encountered a problem when it tried to run. The problem code is 37.
Problem signature:
Problem Event Name: PnPDeviceProblemCode
Architecture: x86
Hardware Id: USB\VID_0BB4&PID_0C92&REV_0100&MI_01
Setup class GUID: {f72fe0d4-cbcb-407d-8814-9ed673d0dd6b}
PnP problem code: 00000025
Driver name: ANDROIDUSB.sys
Driver version: 2.0.7.1
Driver date: 06-10-2009
OS Version: 6.0.6000.2.0.0.256.6
Locale ID: 1033
I am at wits end. It seems that a USB driver for the HTC aria isn't ready yet from the android download site and the drivers from HTC won't work on my computer.
Has anyone else seen anything like this? Is there another way that I can run my apps on my phone?
Thanks,
mhuman1
You may need to manually add a couple of lines to the driver .inf
I did this for an incredible. Search google for "htc incredible usb driver" and use the aria usb pid/id
I modified the driver's inf file like suggested abobe with the following additional text in the two indicated places and now my phone shows up using the "adb devices" command. It shows the serial number of my htc aria.
;HTC Aria
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C92&REV_0100
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C92&REV_0100&MI_01
However, I still can't access the phone from eclipse. Do i still need to do more setup in eclipse?
Thanks,
mhuman1
Htc Aria shows up in DDMS but not as project target
HI,
Now my HTC Aria shows up under the DDMS perspective with its serial number, but I don't know how to make eclipse launch my application on the phone I think that I must be overlooking something really silly.
Thanks,
Keith
Can't install kies on win 7 64bit PC. Installation goes fine, but when starts the first run, the following message comes saying that kies cannot run.
Have uninstalled, rebooted & reinstalled several times.
Also, have tried this "sfc /scannow" from command post to clear any problematic dll's. Still no use.
The Message is as follows.
Problem signature:
Problem Event Name: APPCRASH
Application Name: Kies.exe
Application Version: 1.0.0.413
Application Timestamp: 4ef58477
Fault Module Name: KERNEL32.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdbde
Exception Code: c0000005
Exception Offset: 0001135d
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt
I'm using Win 7 Ultimate 64 bit, no problem
at all.
Suggestion, uninstall, full shutdown, not reboot. Turn off power, pull out power plug for one minute.
Startup again, install Kies (make sure your version is downloaded from Samsung Mobile website which is the same country as your CSC). Do a shutdown again.
Bootup, let your system bootup fully. Plug in your Note and let all the drivers install complete before you start Kies.
Hope the above helps.
Sent from my GT-N7000 using Tapatalk
yeh im using too win 7 x64, so it is something wrong with your computer ;D
Same here no issues for 2 years now.
Maybe redownload and make sure USB debugging isn't check/on
Sent from my GT-I9220 using xda premium
I would do exactly what zard (post #2) is suggesting, I pretty much did the same thing when I had a problem with Kies and it went away.
I have a similar problem.
http://forum.xda-developers.com/showthread.php?t=1490088
I just checked, there's a new version of KIES on the Samsung site (Ver 2.2.0.12014_18_7). I'm on Samsung India. Downloading it right now. I'll report back with results as soon as I install it.
the issue can only be solved with changing the compatibility settings. Enter the properties of the file. Use compatibility with windows XP SP2. Check the admin prev also. Working fine.
Avlrln said:
the issue can only be solved with changing the compatibility settings. Enter the properties of the file. Use compatibility with windows XP SP2. Check the admin prev also. Working fine.
Click to expand...
Click to collapse
matter solved. Thanks
thanks, worked well.
Avlrln said:
the issue can only be solved with changing the compatibility settings. Enter the properties of the file. Use compatibility with windows XP SP2. Check the admin prev also. Working fine.
Click to expand...
Click to collapse
The compatibility mode change didn't work me, but I found this that solved my issue:
http://ramspensieve.blogspot.ca/2011/11/fix-firmware-upgrade-crash-using.html
Kies continues to crash
zard said:
I'm using Win 7 Ultimate 64 bit, no problem
at all.
Suggestion, uninstall, full shutdown, not reboot. Turn off power, pull out power plug for one minute.
Startup again, install Kies (make sure your version is downloaded from Samsung Mobile website which is the same country as your CSC). Do a shutdown again.
Bootup, let your system bootup fully. Plug in your Note and let all the drivers install complete before you start Kies.
Hope the above helps.
Sent from my GT-N7000 using Tapatalk
Click to expand...
Click to collapse
Hello Zard,
---------- Post added at 11:19 PM ---------- Previous post was at 11:01 PM ----------
Hi Folks,
I've been having the same issue. I have win7 64 bit and a Galaxy 3. I followed your instructions and Kies is crashing when I try to open it. I've copied the error from the event log. Does anyone have an idea how to solve this problem?
Log Name: Application
Source: Application Error
Date: 11/4/2012 10:42:54 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
Faulting application name: Kies.exe, version: 1.0.0.893, time stamp: 0x5073d4b9
Faulting module name: msvcrt.dll, version: 7.0.7601.17744, time stamp: 0x4eeaf722
Exception code: 0xc0000005
Fault offset: 0x00009910
Faulting process id: 0x1d1c
Faulting application start time: 0x01cdbb079b25c693
Faulting application path: C:\Program Files (x86)\Samsung\Kies\Kies.exe
Faulting module path: C:\Windows\syswow64\msvcrt.dll
Report Id: e166b3d5-26fa-11e2-bc4d-68b599e60c9c
Event Xml:
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2012-11-05T03:42:54.000000000Z" />
<EventRecordID>45385</EventRecordID>
<Channel>Application</Channel>
<Computer>
<Security />
</System>
<EventData>
<Data>Kies.exe</Data>
<Data>1.0.0.893</Data>
<Data>5073d4b9</Data>
<Data>msvcrt.dll</Data>
<Data>7.0.7601.17744</Data>
<Data>4eeaf722</Data>
<Data>c0000005</Data>
<Data>00009910</Data>
<Data>1d1c</Data>
<Data>01cdbb079b25c693</Data>
<Data>C:\Program Files (x86)\Samsung\Kies\Kies.exe</Data>
<Data>C:\Windows\syswow64\msvcrt.dll</Data>
<Data>e166b3d5-26fa-11e2-bc4d-68b599e60c9c</Data>
</EventData>
</Event>
Thanks for your help,
cestep6
This worked for me
I'm connecting a Samsung Galaxy Note 2 to a pc running Windows 7 Pro x64. Kies would only run in lite mode and crash when I switched to normal mode. Since Kies is really a .Net Framework application, I downloaded and installed the latest (RTM) version of dot Net 4.5 and installed it. Then I ran Windows Update which updated dot Net and in addition, the phone's driver. I rebooted and all ran fine. If you're trying to sync your Galaxy Note 2 with Outlook 2010, remember to make sure that you either start Outlook first or make sure it starts up (automatically) when the Kies software initializes.
Hope this helps someone
naw just uninstall everything of samsunf kies products. Must completely done.then install ccleaner. clean everything and registry.then reboot. and install a new version of kies. I'm sure I has this problem b4. but after I did like a said above everything goes fine.
hooe this helpful
Sent from my GT-N7000 using xda app-developers app
My LG K20 plus will not work and so I am trying to resorting to download mode, but the problem is that every computer fails to recognize it. I have done my research but I still cannot get it to work.
I've already done the following:
Tried different USB data cables
Tried using Windows 7 and Windows 10
Tried using USB2 and USB3 ports
Installed all kinds of drivers, including the official one.
No matter what mode it is on (recovery, download mode, just being turned on, etc.) Windows instantly tells me "USB Device Not Recognized" I'm just really lost and would really love to get my device back in working order.
If this can help anyone figure out my problem, here are the events:
Code:
Device USB\VID_0000&PID_0002\6&162f066f&0&2 was configured.
Driver Name: usb.inf
Class Guid: {36FC9E60-C465-11CF-8056-444553540000}
Driver Date: 06/21/2006
Driver Version: 10.0.15063.0
Driver Provider: Microsoft
Driver Section: BADDEVICE.Dev.NT
Driver Rank: 0xFF0000
Matching Device Id: USB\DEVICE_DESCRIPTOR_FAILURE
Outranked Drivers: usb.inf:USB\DEVICE_DESCRIPTOR_FAILURE:00FF2000
Device Updated: false
Parent Device: USB\VID_8087&PID_8008\5&240b7253&0&1
Code:
Device USB\VID_0000&PID_0002\6&162f066f&0&2 had a problem starting.
Driver Name: usb.inf
Class Guid: {36FC9E60-C465-11CF-8056-444553540000}
Service:
Lower Filters:
Upper Filters:
Problem: 0x2B
Problem Status: 0x0
I am trying to install UbuntuTouch on a new Lenovo X606F. To do this I need to first downgrade from Android 10 to Android 9, but I am failing to do this (I have asked for help on the UBPorts forum but not had any advice so far). I have never flashed any Android system before so its likely I'm making a basic mistake.
I am using
Manjaro Linux (I don't have a Windows system)
SP_Flash_Tool_v5.2152_Linux (I can't use the most recent versions of the flash tool, as they expect an xml file for download, instead of the scatter.txt file that Android 9 has)
Lenovo_Tab_M10_FHD_Plus_TB-X606F_MT6765_S000009_210526_BMP as my Android9 image.
I can't get the Flash Tool to write anything to the tablet at all; I have tried both starting with the tablet off and holding down volume and/or power while connecting the USB, and using 'adb reboot fastboot' after starting download on the Flash Tool. Whichever I do I get the same result:
./flash_tool.sh
QGtkStyle was unable to detect the current GTK+ theme.
sysname:Linux
nodename:gromit
release:5.15.89-1-MANJARO
version:#1 SMP PREEMPT Wed Jan 18 20:37:11 UTC 2023
machine:x86_64
domainame:(none)
cur_kernel_version = 5.15.89
QObject::moveToThread: Cannot move objects with a parent
support_dl_cert_to_storage: 0
Application asked to unregister timer 0xa00001b which is not registered in this thread. Fix application.
Connecting to BROM...
Scanning USB port...
Search usb, timeout set as 3600000 ms
[email protected]/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-2
[email protected]/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-2/1-2:1.0
[email protected]/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-2/1-2:1.1
[email protected]/devices/pci0000:00/0000:00:08.1/0000:04:00.3/usb1/1-2/1-2:1.0/tty/ttyACM0
vid is 0e8d
device vid = 0e8d
device vid = 0e8d
pid is 2000
device pid = 2000
com portName is: /dev/ttyACM0
Total wait time = -1675547049.000000
USB port is obtained. path name(/dev/ttyACM0), port name(/dev/ttyACM0)
USB port detected: /dev/ttyACM0
Connect BROM failed: STATUS_ERR(-1073676287)
Disconnect!
BROM Exception! ( ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00.
[HINT]:
)((ConnectBROM,../../../flashtool/Conn/Connection.cpp,105))
Any idea what I am doing wrong?
Thanks
Graham
Very interesting, I'm looking for the same on my tb125fu.