Kedacom usb device как удалить

Обновлено: 05.07.2024

The package provides the installation files for Google Kedacom KDB Interface Driver version 11.0.0.0.

If the driver is already installed on your system, updating (overwrite-installing) may fix various issues, add new functions, or just upgrade to the available version. Take into consideration that is not recommended to install the driver on Operating Systems other than stated ones.

In order to manually update your driver, follow the steps below (the next steps):

1. Extract the .cab file to a folder of your choice
2. Go to Device Manager (right click on My Computer, choose Manage and then find Device Manager in the left panel), or right click on Start Menu for Windows 10 and select Device Manager
3. Right click on the hardware device you wish to update and choose Update Driver Software
4. Choose to select the location of the new driver manually and browse to the folder where you extracted the driver
5. If you already have the driver installed and want to update to a newer version got to "Let me pick from a list of device drivers on my computer"
6. Click "Have Disk"
7. Browse to the folder where you extracted the driver and click Ok

About ADB (Android Debug Bridge) Driver:

Usually targeted at developers, the ADB (Android Debug Bridge) driver basically allows advanced users to connect any Android mobile phone to a computer and find workarounds for various application problems or even modify the operating system.

Even though this driver is developed for users with a richer ADB command background, it can also be used by regular mobile phone owners, but at their own risk. We recommend that average users make use of this tool wisely, after they have read the step-by-step instructions.

If you intend to install this package, you need to study and understand the installation steps so that no problems are encountered, and to make sure the debug bridge works properly.

Other operating systems might also be compatible, but it’s highly recommendable not to install this driver on platforms other than the ones specified.

That being said, if you wish to apply this package, click the download button and install the driver. Also, make sure you check our website to stay up to date with the latest releases.

It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Углубляясь в познания всех прелестей и чудес Windows 10, столкнулся с не приятным моментом, при установке драйверов для смартфона Lenovo P2 a42, с режимами MTP, PTP и MIDI устройства в принципе все прошло гладко и без дополнительных танцев с бубном, а вот Lenovo ADB Device возникли сложности, он упорно не хотел опознаваться (для тех кто в теме в курсе, что это нужно для прошивки смартфона), и чтобы я не делал, он упорно продолжал опознаваться как Kedacom USB device.
Теперь по порядку:
- самые свежие и актуальные драйвера для Вашей версии смартфона Вы всегда найдете в архиве с прошивкой для него;
- перед установкой драйверов рекомендую отключить проверку цифровой подписи драйверов устройств

1) Нажмите клавиши Win+R на клавиатуре, а затем введите gpedit.msc в окно «Выполнить», нажмите Enter.
2) Конфигурация пользователя
- Административные шаблоны
- Система
- Установка драйвера и дважды кликните по параметру «Цифровая подпись драйверов устройств» в правой части.

- Установить значение «Отключено».

После установки значений, нажмите Применить и Ок, и перезагрузите компьютер

Отключить обновления драйверов из Центра обновления.

1) Нажмите Win+R на клавиатуре, введите gpedit.msc и нажмите Enter.
2) Конфигруация компьютера
- Административные шаблоны
- Система
- Установка драйвера
- Дважды кликните по «Отключить запрос на использование Центра обновления Windows при поиске драйверов»

- Установите «Включено» для данного параметра и примените настройки.

После установки значений, нажмите Применить и Ок

Далее, переведите смартфон в fastboot (перезагрузив смартфон с зажиманием громкость" - ") и подключите смартфон к ПК, открыв диспетчер устройств Вы увидите следующую картинку

Ничего страшного, не отчаиваемся, на водим курсор на "Android Bootloader interface" ПКМ и жмем свойства - и переходим во вкладку драйвера - и откатить драйвер.

Если Вы все проделали правильно, то в конце должны увидеть вот такую картину маслом.

where i can find "android bootloader interface 9.0.0.0 version" ?

I've tried that method installing the LG Driver but no success.
Is there a way to install the driver version 9.0.0 manually, so i can switch to this one?

giant22000

Senior Member

I've been fighting this problem for the last couple of days and have found a solution for myself so I thought I'd share. What fixed it for myself was to manually install the universal driver provided by wugfresh nrt and it's named android_winusb.inf.

This worked for me on multiple N5X's on multiple machines that were refusing to recognize the N5X in bootloader mode as a fastboot device. Hope this helps those who are having problems.

teostar

Senior Member

You could also try doing the process below (another edit), it might work.

If the steps don't work for you, read the edit below.

1. Connect your device while in fastboot mode.
2. open the device manager (ctrl + X on windows 10)
3. find your device "XXX ADB Device"(Mine was "Alcatel ADB Device" but it can be anything)
4. click on the arrow
5. right click on the Android Bootloader Interface
6. Click on "Properties"
7. Go to "Driver" Tab
8. Click "Uninstall"
9. Mark the "Delete the driver software for this device
10. Click OK
11. Disconnect and Reconnect your device from the cable
12. Windows device manager should show an item in the list that simply says Other devices, and will expand to "Android". Do those next steps quickly! (OR: just disconnect from the internet. Some people report it works). You have between 5-10 seconds until Windows changes it to another driver. If device manager changes the driver to "Kedacom USB device" (or something else, start over from step 8).
13. Right click and choose "Update driver software" -> Browse my computer for driver software -> Let me pick from a list.
14. Choose "Kedacom USB device" (or something else that seems logical)
15. Uncheck "Show compatible hardware"
16. Choose "Android bootloader interface version _" that is the latest (should be 28.8.2016).
17. Hopefully it will work for you

Frankly, I'm not entirely sure about step 12 where you have to do it quickly. I have tried it again a few times after succeeding the first time (which showed me this method doesn't always work, very weird), and saw that step 15 doesn't always yield results, especially when you update the driver software of the already "Kedacom USB device" and not "Other devices -> Android". I want to try it again, but I'm scared :laugh:

Edit: In my attempt to figure out the exact steps and what to choose exactly, I tried doing them over and over (starting from 8). Like I said, sometimes it worked and sometimes it didn't (meaning, sometimes I could see the "Android bootloader interface version _" and sometimes I saw something like "%SingleADBinterface" and sometimes I saw "Android bootloader interface". So I guess it's a matter of luck.
If you don't want to rely on luck, what you should do is install the 15 Seconds ADB installer (I did it while I was on bootloader mode, can't remember if device was connected or not) and then start from step 8. Then in the list you should see "Android" (maybe even two) and choose something that makes sense, for me it was "Android bootloader interface". It should then work.

Another edit:
this is a solution provided by @berndblb. Haven't tried it, but it worked for him.
I think I solved it. A post in the OP3 forum was the inspiration:
I think it's not even necessary to uninstall the old driver or disconnect from the internet. Try this and let me know if also worked for you (did for me and I rebooted PC and phone a couple of times).
With the phone connected in fastboot mode open Device Manger
If you have the Kedacom USB device expand it, right click on the driver and go to properties. Probably you have the 11.0.0.0 driver installed. That's the problem.
Right click again, go to Update driver > Browse this computer > let me pick from list > have "show compatible hardware" checked and pick the 9.0.0.0 driver
Bingo. Survives reboots and fastboot works.
Interestingly enough changing the driver to 9.0 also changes the entry in Device manager from Kedacom USB device to Android Device.

I've tried everything here with no luck. Only thing i didnt try is reverting the Kedacom driver to v9.0 no matter what i try i never get an option to choose v9.

---------- Post added at 06:15 PM ---------- Previous post was at 05:26 PM ----------

Ok so i was playing around trying to get the drivers to work and discovered that for a brief second before windows 10 auto downloaded drivers i had fastboot connectivity. I did this by uninstalling (and deleting) the drivers installed. i did NOT unplug the device, but clicked "scan for hardware changes" and it saw it as an android device. So i searched for a way to disable auto download of new drivers and stumbled upon this.

probably not the best option to keep on all the time but it fixed my fastboot options. once i'm rooted and flashed I'll probably turn it back on.

biossone

Member

I've tried that method installing the LG Driver but no success.
Is there a way to install the driver version 9.0.0 manually, so i can switch to this one?

I have manually installed the driver (find with google) and then windows auto update to 11.0.0.0 i roll back to old version and it works.
Sorry for bad english [emoji28]

Sent from my Nexus 5X using XDA-Developers mobile app

theLazyGeek

Member

Samsung USB driver pack available at Samsung's Developer website should do it. It's a 15MB download I'd guess and that generally does the trick.

biossone

Member

I have installed Lg driver first, and then "android bootloader interface version 9.0.0.0" (found with google)

Sent from my Nexus 5X using XDA-Developers mobile app

UszkiX

Senior Member

I have installed Lg driver first, and then "android bootloader interface version 9.0.0.0" (found with google)

Sent from my Nexus 5X using XDA-Developers mobile app

Can you share a link for drivers?
Ugh.. its my 3rd try and still fastboot not detecting phone.

Wysłane z mojego Nexus 5X przy użyciu Tapatalka

biossone

Member

Can you share a link for drivers?
Ugh.. its my 3rd try and still fastboot not detecting phone.

Wysłane z mojego Nexus 5X przy użyciu Tapatalka

Sorry but don't remenber the link. i searched "android bootloader interface version 9.0.0.0" on google

Sent from my Nexus 5X using XDA-Developers mobile app

UszkiX

Senior Member

Sorry but don't remenber the link. i searched "android bootloader interface version 9.0.0.0" on google

Sent from my Nexus 5X using XDA-Developers mobile app

How to install this?

Wysłane z mojego Nexus 5X przy użyciu Tapatalka

Einherjer*

Senior Member

I have manually installed the driver (find with google) and then windows auto update to 11.0.0.0 i roll back to old version and it works.
Sorry for bad english [emoji28]

Sent from my Nexus 5X using XDA-Developers mobile app

I only find a "20855130_dae427ffe0a2d6268aa209d782d05ea874aad0dc.cab" file.

biossone

Member

Hi there, i got the same "Kedacom USB Device" on Windows 10 Pro x64 and if i want to pick the 9.0.0.0 driver it is not there.
Driver 11.0.0.0 is installed. I tried the workaround but no luck. I only find a "20855130_dae427ffe0a2d6268aa209d782d05ea874aad0dc.cab" file.

follow the step written above ( go to fastboot, unistall driver, replug ecc ecc.) but when you have to upload driver, use the driver from the link. When reconnect to internet windows auto-update to 11.0.0.0 and now you have to restore 9.0.0.0 .
Sorry again for english.

Einherjer*

Senior Member

Thanks. I can confirm, this works on my Windows 10 x64 machine!

berndblb

Inactive Recognized Contributor

L0RD_SkyWalK3R

New member

Got an alternative method (especially for win 10 which)

You could also try doing the process below (another edit), it might work.

If the steps don't work for you, read the edit below.

Читайте также: