Develop Bugs

[SIGNED DRIVERS x64] Eugenia Project MTTY USB SIGNED Driver for Windows Vista/7 x64

Hi all, I'm the Eugenia Project developer!
As you know, for making your device to work with mtty on Windows Vista or Windows 7, you had to reboot, disable signed driver control, install the driver and go on with mtty.
Ouh, and after a reboot you'll get a not working device if you don't restore the "old - new" driver!
From now, you won't have this problem anymore!
With the Eugenia USB x64 Signed Driver you will only install the driver without any reboot or disabling driver signature controls, and it works even after rebooting!
This driver will work with MTTY and RUUs (including CustomRUUs) flawlessly and without any complicated procedures!
What's included in the package:
*- A signed certificate for the driver,
*- The driver,
*- The installer.
Installing the driver:
*- Decompress the archive
*- Make sure your device isn't connected to USB
*- Run the file named "RunThis"
*- Connect your device to USB.
If the device won't work, you have to tell your system to use the new driver.
To do that (on Windows 7):
*- Right click on Computer, then click Properties.
*- Click on Device Manager
*- Expand "Mobile devices" and double click HTC USB Sync (or unknown device if it is recognized like that)
*- Click on the "Driver" tab, then click on the "Update Driver..." button
*- Click on "Browse my computer for driver software", then on "Let me pick from a list of device drivers on my computer"
*- Click on "Have disk..." and select the driver in the folder where you've uncompressed the archive.
*- Double click on Eugenia HTC USB Sync
It will say that it's not digitally signed from Microsoft, but install it anyway. It will work.
As the result, you'll have.....
....screenshot:
Download:
Version 1.0: EternityProject Website
Hope you like it!

Well I will try, because from now I use VMWare to Flash in Win7 x64 !

I don't know if it work, because finally Windows found a driver on windows update and install it (11.9 Mo, if I remember).
I flash a new ROM and it's OK !

I am using Windows 7
trying to install the driver, and go into the device manager.
I can not find "mobile device" from the list. why?
What next to ensure it is using that driver?

Hi,
i ust tryed this and it didnt install anything, it just said the driver was present and didnt do anythin.
when i checked my device manager it didnt say "Eugenia HTC USB Sync"als when i tryed using the driver without restarting and pressing F8 to remove the Driver signing, MTTY doesnt show USB.
could this be because there s already a working driver?
Thanks for help
MG

That what I've done:
1. Reset my diamond to bootloader.
2. Connect to my win 7 x64.
3. The HTC Usb sync appears in Device Manager.
4. Update to your Eugenia USB driver.
5. Done .
But the connection in bootloader mode doesn't change to usb - it's serial - I can't use mtty.
PS: My norton AV 2009 detected security risk in Runthis.exe and removed it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

jamit018 said:
I am using Windows 7
trying to install the driver, and go into the device manager.
I can not find "mobile device" from the list. why?
What next to ensure it is using that driver?
Click to expand...
Click to collapse
Ya same here i installed it and could not flash rom before i was able to flash in "signature disabled"mode but now it also don't work... i can not find the mobile device in the list it just said unknown device ... the only i got around was by running back up in PC and going bacck to the time before installing this driver...

On my 3 PCs running Windows 7 x64 all works.
Don't worry about the antivirus warning, it's all clean.
It recognizes it as a virus because the .exe file is compiled from a batch, but I repeat, it's all virus free.
However, have you tried to tell to your PC that it MUST use the Eugenia USB Driver?
I mean in Device Manager!
I'm using it right now on my HTC HD2 (Leo) for playing with the stock SPL and it works flawlessly even on that device.
Let me know...
IF it still doesn't work, I'll retest all on other PCs.
P.S.: As the last "hope", try to delete the old drivers used without the signature enforcement

Workls like a charm for me!

Guys the download link is no longer working... Can someone please re-upload?

i've hit 3 issues:
(1) I ran runthis.exe as non-admin by accident.. ran it again as admin and got error that cert already existed etc but the problem is:--
(2) "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)". the device works 'ok' when i boot win7 x64 into disable driver check via f8
(3) but mtty stops responding when i type 1 letter
but this looks good! thank you for your work

binary64 said:
i've hit 3 issues:
(1) I ran runthis.exe as non-admin by accident.. ran it again as admin and got error that cert already existed etc but the problem is:--
(2) "Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)". the device works 'ok' when i boot win7 x64 into disable driver check via f8
(3) but mtty stops responding when i type 1 letter
but this looks good! thank you for your work
Click to expand...
Click to collapse
Hi,
for Windows 7 x64 try the driver install on post 3 here
MG

works perfectly on my Win 7 RTM x64 !

[Q] ADB doesn't detect my phone

Hi,
I have a stock unrooted Desire Z, and I'd like to root it using the instructions provided here.
I've downloaded gfree and visionary r14, and I already have the Android SDK installed, along with adb. However, for some reason, adb doesn't detect my phone when connected. It's set to "Charge only" and "USB debugging" is also enabled. I've already installed HTC Sync, however Device Manager still shows an "Android Phone" under "Other devices" as shown below
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've tried to install the driver again but I'm not sure where to point it. I've tried pointing it to the <sdk>\google-usb_driver\ but it couldn't find any appropriate driver. I looked at android_winusb.inf and sure enough I don't find my Desire Z in the list of USB VID/PIDs.
I've also tried installing the drivers in <HTC>\HTC Driver\Driver Files\XP_x86, <HTC>\HTC BMP USB Driver\qcusbmdm, or <HTC>\HTC BMP USB Driver\qcusbser, but none of them worked.
Lastly, I've tried uninstalling the "Android Phone" driver(it's not installed in the first place, but just to get it out of device manager), but once I reconnected the phone, "Found New Hardware Wizard" comes up again prompting me to install a driver for it.
Is this the reason why my phone isn't being detected? How can I install the correct driver and get adb to detect the phone properly?
Thanks!

In before you get flamed and this thread gets locked.
ZOMG yoo didn't search DIAF!!!!!111one
BTW there is a Q&A forum which is really the right place for issues like this (http://forum.xda-developers.com/forumdisplay.php?f=829)
To answer your question, yes it's a driver issue. The drivers do seem to be tricky what worked on my work laptop (Windows 7 x86) did not work on my home laptop (Vista x64)
Are you using this guide? http://forum.xda-developers.com/showthread.php?t=865685
You can also try this guide: http://forum.xda-developers.com/showthread.php?t=834748
There is a driver in that one that worked on my Windows 7 machine: http://www.mediafire.com/?wzdjcmowziw
There is another one to try but I can't remember where it is, the search function isn't working right now and as I mentioned this thread will likely be locked soon.
Are you using "Update Driver" from device manager, then using "Have Disk" and pointing it to the folder where you have the driver extracted?
If you still need help PM me I will look for that other driver.
Edit: this may also be helpful

raitchison said:
BTW there is a Q&A forum which is really the right place for issues like this (http://forum.xda-developers.com/forumdisplay.php?f=829)
Click to expand...
Click to collapse
right, not dev related, moved to q&a

Anyone know how I can get ADB on WINXP? doesn't work for me.
Sent from my HTC Vision using XDA App

What part isn't working? Does the SDK refuse to install or are you getting some kind of error.
Without more information I could offer the first google search result for "adb xp" http://forums.t-mobile.com/t5/Operating-System-Software/How-to-Install-ADB-XP-and-Vista/m-p/163836
It seems a bit dated but may be helpful all the same.

Ok thanks. When I first rooted my G2 I tried with ADB but didn't work for me. I don't think. So I went with visionary. The easier way? I keep hearing ADB is like a must so we could see exactly what we're doing. How about that ADB wireless app? Does anyone use that and is it good?
Sent from my HTC Vision using XDA App

Hi raitchison, thanks for the reply.
I've not followed those 2 guides specifically, but rather googled and found other guides, and followed them(the general gist).
In the first guide's "complete" way, I've completed Steps 1, 2, 3, 5.
Didn't do 4 but rather just went to the platform-tools folder and ran adb directly from there. Shouldn't matter.
I'm using a 3rd party cable, didn't think it'd make a difference but I guess I'll try with the original cable as well. This cable seems to work on another PC(at least driver installation, haven't tried with adb yet) with the same OS(Windows XP Pro SP3)
Step 7 doesn't show any devices. That's the problem.
Did a similar installation with the "quick" way. Same problem. The 2nd link seems to be similar.
I'm using Device Manager->Android Phone->Update Driver->Install from a list or specific location(Advanced)->Include this location in the search-><Path> where <Path> is the location of the drivers that I tried(from SDK or HTC Sync). Windows tells me that there's no appropriate drivers in that path to install.
Also tried Device Manager->Android Phone->Update Driver->Install from a list or specific location(Advanced)->Don't search. I will choose the driver to install->Other devices->Have Disk-><Path>. Same problem.

Are you sure you installed the latest HTC Sync (linked to in the guide referenced earlier)? Otherwise, you can try installing PdaNet (it'll install the correct drivers as well---a lot of users have reported success with it). You can also try using the drivers attached to this post. It is simply the SDK drivers modified with the ID for the G2:
Code:
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01
I think it should work with the Desire Z as well, but I'm not sure...

What version of Windows are you using ? The HTC Sync drivers should give you everything you need. It does sound like it's installing using the wrong driver, and that's why it's not seeing it.

steviewevie said:
What version of Windows are you using ? The HTC Sync drivers should give you everything you need. It does sound like it's installing using the wrong driver, and that's why it's not seeing it.
Click to expand...
Click to collapse
The HTC Sync drivers did not work on my home PC, which is Vista x64, I had to use a different driver to get it to work.

raitchison said:
The HTC Sync drivers did not work on my home PC, which is Vista x64, I had to use a different driver to get it to work.
Click to expand...
Click to collapse
Vista 64 ? ok, that's probably not that common though. The HTC Sync drivers do work with Win 7 64-bit, because I walked a guy through it myself. So I'm suprised they don't work on Vista 64 as well (but I don't doubt you).

Windows Phone Driver Error

I'm suddenly having a problem with my Nokia Lumia 800. For some reason my PC is failing to install the Windows Phone 7 portable device driver. I get an "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)" error.
I've tried un-installing the drivers and reinstalling them but I still get the same problem? Any ideas? Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

mickfarr said:
I'm suddenly having a problem with my Nokia Lumia 800. For some reason my PC is failing to install the Windows Phone 7 portable device driver. I get an "This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)" error.
I've tried un-installing the drivers and reinstalling them but I still get the same problem? Any ideas? Thanks
Click to expand...
Click to collapse
Make sure that you have the automatic driver downloading from Windows Update turned on. You can turn it on in the "Installing device drivers" screen when you plug in a USB device.

jessenic said:
Make sure that you have the automatic driver downloading from Windows Update turned on. You can turn it on in the "Installing device drivers" screen when you plug in a USB device.
Click to expand...
Click to collapse
No luck with that.

Uninstall the drivers for Windows Phone 7 and Windows Phone USB.
Restart the PC and then attach the phone.
Try to use a different USB port.
If that don't work then i'd suggest a new USB cable

I've tried a different USB cable that's working with another Nokia Lumia 800 in the office and still the same problem. I've tried different USB ports and I've also tried this USB Cable and Lumia on a different PC and it installed the drivers correctly and worked fine.
Is there any settings that I may have changed that could have casued the error code 31. The phone charges up fine from the USB port, what ever is causing the 31 error is the problem?

mickfarr said:
I've tried a different USB cable that's working with another Nokia Lumia 800 in the office and still the same problem. I've tried different USB ports and I've also tried this USB Cable and Lumia on a different PC and it installed the drivers correctly and worked fine.
Is there any settings that I may have changed that could have casued the error code 31. The phone charges up fine from the USB port, what ever is causing the 31 error is the problem?
Click to expand...
Click to collapse
Try this:
Unplug your phone
Uninstall Drivers
Uninstall Zune
Reboot
Install Zune
Plug your phone

Tried that and I still have the same problem!

Hi,
Search google on how to uninstall disconnected devices in windows and remove the old device( something like "show_nonpresent_devices" in device Management. )
Sorry for previty, can't search the Link right now
Regards
Donpromillo

i had this issue with my Focus. It was the USB Plug on my phone. I did an warranty exchange. The Rep tried it with his usb cable on a computer in the store and got the same error.

Did you try to use the Windows Troubleshooter ?

Strike_Eagle said:
Did you try to use the Windows Troubleshooter ?
Click to expand...
Click to collapse
One of the most useless pieces of windows 7 "help" I've seen. I like the "help" it provides in diagnosing wifi errors. Priceless.
A quick google of the error showed me its a port problem on the phone.

ohgood said:
One of the most useless pieces of windows 7 "help" I've seen. I like the "help" it provides in diagnosing wifi errors. Priceless.
A quick google of the error showed me its a port problem on the phone.
Click to expand...
Click to collapse
There's nothing wrong with the phone, its the PC.

bennyj71 said:
i had this issue with my Focus. It was the USB Plug on my phone. I did an warranty exchange. The Rep tried it with his usb cable on a computer in the store and got the same error.
Click to expand...
Click to collapse
The phones fine, its the PC I have the problem with.

donpromillo said:
Hi,
Search google on how to uninstall disconnected devices in windows and remove the old device( something like "show_nonpresent_devices" in device Management. )
Sorry for previty, can't search the Link right now
Regards
Donpromillo
Click to expand...
Click to collapse
Great idea! I didn't think of that. It's my office PC so I'll give it a go on Tuesday when I'm back in the office.
Thanks!

ohgood said:
One of the most useless pieces of windows 7 "help" I've seen. I like the "help" it provides in diagnosing wifi errors. Priceless.
A quick google of the error showed me its a port problem on the phone.
Click to expand...
Click to collapse
Not at all.
It helps me solve several problem with driver on Windows 7.
It is useless most of the time but it is useful sometime...

[EDITED]
WINDOWS TROUBLESHOOTING STEP-BY-STEP SOLUTION
(Step 0: Install zune)
e driver. To do this, follow these steps:
1. Click Start, right-click Computer, and then click Properties.
2. Click Device Manager, located in the left column.
3. A window will appear with the name of your computer and a list of files. If you don't see the files, click the name of your computer. The name of your Windows Phone should be listed under Portable Devices. If Windows Phone was incorrectly installed, it may be listed with a yellow exclamation mark . Or, it may be listed under Other Devices as a USB device or an unknown device.
4. On the Driver tab, click Uninstall.
5. Select Delete the driver software for this device and then click OK.
6. Return to the Device Manager window, click the Action menu, and then click Scan for hardware changes.
7. Open Portable Devices, double-click the name of your Windows Phone, and then click the Driver tab. Or, if you don't see your phone name, click unknown device listed under Other Devices, and then click the Driver tab.
8. Click Update Driver.
9. Click Browse my computer for driver software.
10. Click Browse, locate on the C drive the Program Files/Zune/Drivers folder, and then click OK.
11. Click Next and if you're prompted, click Install. You may only be given a Close option.
12. After the driver installation is complete, Close the open windows until you exit the Device Manager. If you're prompted to restart your computer, do so when you can.
(13. (In case of syncing problems) Go to Program Files/Zune and find Zune.exe, right click, select properties, then Compability, check run as administrator and hit ok. Run Zune a gain, and an admin prompt will appear)
Sent from my rooted SGS i9000 running Gingerbread. I also know stuff about WP7.5 and Zune.

Please just follow the steps and ignore the text between step 0 and 1. I edited the message too many times and can't cut it out.
Sent from my rooted SGS i9000 running Gingerbread. I also know stuff about WP7.5 and Zune!

Firemil said:
Please just follow the steps and ignore the text between step 0 and 1. I edited the message too many times and can't cut it out.
Sent from my rooted SGS i9000 running Gingerbread. I also know stuff about WP7.5 and Zune!
Click to expand...
Click to collapse
Tried all that and when I try to install the drivers from the Zune driver directory it tells me that my driver is up to date.

donpromillo said:
Hi,
Search google on how to uninstall disconnected devices in windows and remove the old device( something like "show_nonpresent_devices" in device Management. )
Sorry for previty, can't search the Link right now
Regards
Donpromillo
Click to expand...
Click to collapse
I set the device to display all the non present device drivers and I uninstalled loads!! I had old HTC Android drivers, HTC HD2, Nokia Lumia and even Blackberry not that I've ever had a blackberry
I unistalled all the USB storage drivers for windows phones and android etc and also the USB Composite drivers. This is the closest I've got to getting it to work but it is still not working.
My Lumia was working fine on this PC until I downloaded the Nokia care suite. I'm wondering if I did something them but I can't remember?
EDIT: Nokia Care Suite is picking up my Nokia Lumia 800 when connected just not Zune?

Help me, please!
I want restore/Install booloader to QLOAD/Qcom but:
NSS not find my phone.
NSS 0.47.0 Beta - Quick Install & Restore of the 710 bootloader - xda-developers

adb drivers in Win7 64

I have no problem connecting my Epic 4G Touch to a WinXP system with adb.
On Win7 64, I installed Kies, but when I plug the phone in, I am told that no drivers for CDC Serial and SAMSUNG_Android were found. And "adb devices" finds nothing.
I can mount the device just fine for transferring files. But I need adb for software development.

arpruss said:
I have no problem connecting my Epic 4G Touch to a WinXP system with adb.
On Win7 64, I installed Kies, but when I plug the phone in, I am told that no drivers for CDC Serial and SAMSUNG_Android were found. And "adb devices" finds nothing.
I can mount the device just fine for transferring files. But I need adb for software development.
Click to expand...
Click to collapse
Unless you're going to use it, I would uninstall KIES. Having it running in the background can mess up other functions like flashing with odin. I would just install the Samsung Drivers by themselves. It worked for my adb install in windows 7.
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe

tdunham said:
Unless you're going to use it, I would uninstall KIES. Having it running in the background can mess up other functions like flashing with odin. I would just install the Samsung Drivers by themselves. It worked for my adb install in windows 7.
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Click to expand...
Click to collapse
Just did that. Uninstalled KIES and tried to install the driver package. Driver installer says: "The MSS Installation for SAMSUNG USB Driver for Mobile Phones V1.3.2360.0 has failed."
Were you using 64-bit Win7?

arpruss said:
Just did that. Uninstalled KIES and tried to install the driver package. Driver installer says: "The MSS Installation for SAMSUNG USB Driver for Mobile Phones V1.3.2360.0 has failed."
Were you using 64-bit Win7?
Click to expand...
Click to collapse
Uninstall all your drivers from device manager and start fresh. Only install the driver.exe from samsungs support page. Once that is installed plug your phone in and let it run through the drivers before you try anything else.
If your computer isn't recognizing your phone in the first place then it's not a problem with adb, its the drivers, so start there.

OK, so I uninstalled KIES and the drivers.
I then tried to install the drivers. No go: The installer continues to fail, with the progress bar at around 80-90%. I experimented with running the installer as administrator, installing off of \Program Files (x86) and off of \SAMSUNG, instead of the default \Program Files, and still no go.
I then re-installed KIES, turned off debug in the phone, and plugged it in. Win7 installed a driver for the phone and all was well.
I then unplugged the phone, turned on debug, and plugged it back it. Now Win7 installed the following drivers:
Code:
USB Composite Device
USB Mass Storage Device
Android UMS Composite USB Device (two of these!)
and said they're ready to use. But it also tried to install:
Code:
CDC Serial
SAMSUNG_Android
and it gave "Driver not found" for these.
And "adb devices" lists nothing.
To make sure adb works fine I then plugged in a Kindle Fire. Windows set up the drivers for it and it showed up in "adb devices" just fine.

I still can't get it working.
I even tried using the advice I saw on some blog to use the Device Manager, and then update the non-working devices by directing Windows to look in the "\Program Files (x86)\SAMSUNG\USB Drivers" directory for drivers. No effect--Windows says it can't find an appropriate driver there.
The 25_escape\ssudadb.inf file seems to contain stuff with hardware IDs that match the device that Windows can't find a driver for. BUT there is no x64 section in the inf file. Is there supposed to be one?
I even tried turning off Windows' driver signature checks. Didn't help.
Does anybody have this working 64-bit Win7?

arpruss said:
I still can't get it working.
I even tried using the advice I saw on some blog to use the Device Manager, and then update the non-working devices by directing Windows to look in the "\Program Files (x86)\SAMSUNG\USB Drivers" directory for drivers. No effect--Windows says it can't find an appropriate driver there.
The 25_escape\ssudadb.inf file seems to contain stuff with hardware IDs that match the device that Windows can't find a driver for. BUT there is no x64 section in the inf file. Is there supposed to be one?
I even tried turning off Windows' driver signature checks. Didn't help.
Does anybody have this working 64-bit Win7?
Click to expand...
Click to collapse
Have it working - and did remember I have Kies installed.
Maybe I downloaded both the separate driver and Kies?
USB Driver Link:
http://org.downloadcenter.samsung.c...342248/Sprint_d710_USB_Driver_v1_3_2360_0.exe
Kies Link:
http://org.downloadcenter.samsung.c...0111012045653670/KiesPC_2.0.3.11082_152_4.exe
Know I have problem still with Kies... but I can use ODIN without issues.

Finally got it!
I can't really explain how I did it, as there was a lot of trial and error and I wasn't keeping notes. But the basic trick was to right click in device manager on the unknown SAMSUNG_Android device, choose Update Driver, choose "Let me pick", choose "Have disk", point to the "SAMSUNG\USB Drivers\25_escape" folder from the KIES installation, and then choose "Samsung Mobile USB Composite Device".
You may then get another unknown device, which using the same method you set to ADB. I did a bunch of stuff in different ways, trying to match different drivers from the 25_escape folder to different devices, until it finally worked.

Same issue, solved twice
I have had similar problems in win7 64bit twice now. I got it working once, then ended up reinstalling windows for other reasons. I then had the same problem when trying to install cm9alpha3.
Both times it took a strange combination of installing the drivers manually, plugging in the phone, etc. to get it working. The best advice I have for others is to keep trying.
Also, it seems that Kies almost never gets it right. I personally don't even keep it installed.

I posted a guide on how I got this working.
adb works, but I still can't connect to KIES.

arpruss said:
I posted a guide on how I got this working.
adb works, but I still can't connect to KIES.
Click to expand...
Click to collapse
What Rom are you on. I had same problem with phone running on Calks E4GT v. 3.0 GB Rom, Kies won't recognize Calks Rom, wifeys stock Epic is recognized no problem . Pc Asus G73 win7 64. PC recognizes my phone but Kies won't.
Pp.
Edit
It is rumoured that Kies w will only recognize stock roms.
Pp.
Sent from my tofu plasma converter.

PanchoPlanet said:
What Rom are you on. I had same problem with phone running on Calks E4GT v. 3.0 GB Rom, Kies won't recognize Calks Rom, wifeys stock Epic is recognized no problem . Pc Asus G73 win7 64. PC recognizes my phone but Kies won't.
Pp.
Edit
It is rumoured that Kies w will only recognize stock roms.
Click to expand...
Click to collapse
I am on stock EL29, no root.
It worked once on my WinXP system, but now it doesn't work on either the WinXP or Win7 system.

Oops. I misunderstood the KIES error message to mean that I'm supposed to have the phone in adb mode for KIES to work. But actually adb mode needs to be off for KIES to work. Now it works fine.

arpruss said:
Oops. I misunderstood the KIES error message to mean that I'm supposed to have the phone in adb mode for KIES to work. But actually adb mode needs to be off for KIES to work. Now it works fine.
Click to expand...
Click to collapse
hi, I have same issue with you now, can you teach me how to solve it? thanks.
WIN7 x64 with GT-I9300

Just turn off USB debugging and Kies will connect.
Sent from my SPH-D710 using Tapatalk 2

Chrome DevTools Inspect working again
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I couldn't get Chrome Dev Tools to remote debug (chrome://inspect) until I installed the "Android Composite ADB Interface" (just picked the latest version). See screenshot attached (taken before I installed correct driver).
1. To install I right-clicked on the "SAMSUNG_Android" driver under "Other Devices" in the Device Manager.
2. "Update Driver Software..."
3. "Browse my computer for driver software"
4. "Let me pick from a list of device drivers on my computer"
5. Select "Samsung Android Phone"
6. Select "Android Composite ADB Interface Version" (latest one)
7. Ignore warning that Windows does not know if this driver is compatible.
At this point, I saw the "Trust this device" message come up on the Samsung phone
Thanks for the help. This was really killing me as I had tried everything including installing the official drivers from Samsung's site (developer.samsung.com/technical-doc/view.do?v=T000000117)
Note: I don't have Windows Kies installed and I am using Windows 7 x64 OS. Also note that this does not fix the "CDC Serial" error, however, this is not required for remote debugging over USB.

My PC wont recognize the tablet

I bought the new N7 and wanted to make a backups from my old N7. So for that I used the Helium app and had to switch between the devices when connected via USB to my PC. At first my PC recognized the new N7 and I could see my tablet as a removable drive, but then something happened and now when I plug my new N7 to my PC, it wont pop up a removable drive as it used to. I installed ADB drivers but it doesnt help.
I assume something got ****ed up while I constantly switched between my 2 tablets.

Do you see the N7 in the Windows Device manager?
Do you still have MTP enabled?
Do you have USB Debugging Enabled?

Having the same problem here. My PC (running Windows 8 x64) does not recognize my Nexus 7. USB debugging and MTP are both turned on. I am only seeing an "unknown device" in the device manager. I get this error on the PC:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I had the same with both Windows 7 and 8 (both 64 bit).
I found the solution by editing the "android_winusb.inf" file.
Can you check the Hardware-id's for your N7 in the windows device manager?
For me I found that this changes when I enable/disable MTP.
But in both cases the id's were not listed in the inf file.
Like I said I had the same issue on Windows 7 and 8.

Schaduwridder said:
I had the same with both Windows 7 and 8 (both 64 bit).
I found the solution by editing the "android_winusb.inf" file.
Can you check the Hardware-id's for your N7 in the windows device manager?
For me I found that this changes when I enable/disable MTP.
But in both cases the id's were not listed in the inf file.
Like I said I had the same issue on Windows 7 and 8.
Click to expand...
Click to collapse
I had a similar issue yesterday, and I had to reinstall the drivers on my PC. I deleted the drivers from Device Manager, shut the N7 down, and restarted it. This triggered Windows to reinstall the drivers.
Rick

For me the only solution was tot add soms extra lines/hardware id's to the driver inf file.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Schaduwridder said:
For me the only solution was tot add soms extra lines/hardware id's to the driver inf file.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the same problem. My w7 64 bit laptop connected fine till I rooted the nexus 7. Now, ptp connection works but when I switch to mtp, I too don't get the popup that lets me transfer files. I'm sure that the windows 7 mtp driver has been disabled or deleted in some way when the adb driver was installed.
- What extra lines/hardware ids did you add to correct the problem?
- Which driver inf file?
- What is the name of the driver file in question.
Thanks.

Anderson2 said:
I have the same problem. My w7 64 bit laptop connected fine till I rooted the nexus 7. Now, ptp connection works but when I switch to mtp, I too don't get the popup that lets me transfer files. I'm sure that the windows 7 mtp driver has been disabled or deleted in some way when the adb driver was installed.
- What extra lines/hardware ids did you add to correct the problem?
- Which driver inf file?
- What is the name of the driver file in question.
Thanks.
Click to expand...
Click to collapse
I checked the hardware id in the Windows Device manager.
There my device was recognised as a Nexus 7 but it showed the yellow exclamation mark that the device wasn't functioning correctly.
For me the hardware-id is: USB\VID_18D1&PID_4EE2&MI_01
Then I opened the file "android_winusb.inf" in Notepad.
I couldn't find this hardware-id in the file anywhere.
I went to the section: [Google.NTamd64]
Then duplicated the last line of this section and changed the ID to the one I found in my Windows Device Manager.
Then I could install the driver correctly.
Because I am on Windows I had to bypass the Windows 8 Driver check since the driver is no not correctly signed anymore.
This was I finally had the N7 correctly installed for ADB so I could Unlock and Root.
I also noticed the the Hardware ID changes between having MPT ON or OFF while USB debugging was ON.

Not sure what I did, but I am now able to get the Nexus 7 drivers working on Windows 8 x64. It's odd because the tablet is only recognized via Windows and adb when I'm in PTP mode, and once I switch over to MTP mode, it stops working. I can only view the contents of the /DCIM/ and /Pictures/ directories of the "SD card" in Windows Explorer when in PTP mode.

beanboy89 said:
Not sure what I did, but I am now able to get the Nexus 7 drivers working on Windows 8 x64. It's odd because the tablet is only recognized via Windows and adb when I'm in PTP mode, and once I switch over to MTP mode, it stops working. I can only view the contents of the /DCIM/ and /Pictures/ directories of the "SD card" in Windows Explorer when in PTP mode.
Click to expand...
Click to collapse
I have noticed that the device id changed when enabling/disabling MTP. Both id's should be known to the driver for things to always work OK.