Database Develop

[Q] USB Debugging/Mass Storage Mode connection to computer issue

Hello folks,
I'm facing this "please insert a disk" issue when connecting my Note to computer via USB Debugging mode / Mass Storage Mode.
I'll let screenshots in the attachment explain itself. #1 shows the screenshot of devices menu when the phone is plugged into the computer in DEBUG mode; #2 shows the screen after I've clicked "connect USB storage" from the drop-down list of the phone; #3 shows what happens when I try to open one of the two "removable disks".
MTP mode works fine, as well as Kies connection. As I finally started exploring the potential of Android platform, I realized that MTP and Kies connection are the most useless connection options for me, and I'd rather leave it in debug mode all day. So has anybody experienced this issue, or had any suggestion on the solution?
As always, many thanks in advance, and many thanks button clicks afterward!
p.s.,
Desktop OS: Win7 Pro X64 SP1
Note: 2.3.6 Stock LB1 Open Germany Firmware, CF rooted LB1 kernel.
Also, I should have all the latest official device driver from Samsung, as I have the latest version of Kies installed (and I discovered a driver folder under Kies' installed location). I'm not so sure about adb driver, but I was able to find the Note to be listed under devices by typing "adb devices". So.. I don't know where could've gone wrong.

Help anyone?

This really sounds weird... I was facing problems of the Galaxy Note not being detected on several Windows7 32/64-Bit SP1 computers as well but this was gone after I installed SAMSUNG_USB_Driver_for_Mobile_Phones.
You are right - from all that i know all required drivers should be available when KIES is installed on your system. Whatis even more strange is that your device seems to be detected as two partitions are available and are displayed in Explorer...
So I would test the following:
- check if your device manager lists any unknown devices
- Uninstall KIES and try to find the SAMSUNG_USB_Driver_for_Mobile_Phones and install those
- check all available USB ports and see if this solves the problem
- try another USB cable
- make sure your (external) SD card is formatted with a Windows compatible file-system e.g. FAT32
Hope this is helpful and helps solving your problem.

Thanks for your reply!
My device manager basically listed all the drivers/devices associated with the phone:
My Device manager shows devices:
Samsung Android Composite ADB interface
Android UMS Composite USB device (x2)
SAMSUNG Android USB Modem
USB Mass Storage Device
USB Mass Storage Device (Android)
I've attached the screenshot when all the drivers being installed when the phone is firstly connected to the computer. Also in the device manager, everything shows "this device is working properly"
I then decided to test with another Note of my friend's (On the same computer). Her Note has no SD card in it, and is completely stock ROM non-rooted LA4 Open Germany firmware. The same thing happened.
One thing worth mentioning: Yesterday, this worked only for once. When I initially encountered this issue, I restarted my computer, and boom, my phone was connected in Debugging mode! However, once disconnected, and I tried to connect it to the computer again, this issue came back. And afterward, no matter how I restart my computer, the phone won't get connected.
I also tried all USB port (USB 2.0 and 3.0), three different cables (2 of them are Samsung OEMs) and failed to address the issue.
I'm nearly exhausted but I will never give up, as this is my only computer and my only phone (haha), and without solving this issue, I'm never gonna be able to view the phone as a USB storage and easily transfer the file from my computer to the phone.
I'm going to try the last thing that I haven't done from the list you posted:
- Uninstall KIES and try to find the SAMSUNG_USB_Driver_for_Mobile_Phones and install those
I believe that I can keep the driver folder in the Kies' folder, as I believe those are the newest Samsung driver, given that the Kies was the latest release version.
So far, I can only conclude that this issue is not related to specific phone but the Windows 7.
And thank you for your help btotaku!
If anyone has any insight into this issue, please help me. Thumbs up for you!

BTW, I was able to extract both SAMSUNG_USB_Driver_for_Mobile_Phones.exe from under Kies' installation path under Program Files x86 folder, and an uncompressed folder of all kinds of drivers for Samsung device, called "USB Drivers".
And looks like I was wrong. The newest version of SAMSUNG_USB_Driver_for_Mobile_Phones I had was 1.4.8. While the driver that came with the newest Kies was 1.4.103
I'll post back soon

Reinstal Windows on your PC bro.
Problem fixed.

is that your internal memory or the sd card?

Same thing happens either with SD card in the phone or not

avetny said:
Reinstal Windows on your PC bro.
Problem fixed.
Click to expand...
Click to collapse
That's the last thing I would do

Fastboot USB error: A request for the USB BOS descriptor failed

Hello all,
I got an old 5830 Galaxy Ace I wanna hand over to a friend. I want to flash stock ROM onto it.
When I start the phone normally I can connect via USB cable and see the files on the device.
However when entering 'downloading' mode (power+volume down+home) I get the error: This device cannot start. (Code 10) "A request for the USB BOS descriptor failed." (copied from Device Manager properties of Samsung USB Composite Device). I also see this ballon pop in in the sys tray
The device does NOT show up in either Odin or Flashtool.
I am on Win 8.1 64bit laptop. I have searched and trawled the internet already and did the following:
- disabled signature verification in startup options of windows
- installed fastboot drivers via flashtool
- installed Samsung USB drivers
- tried 4 different USB ports and two different cables (and also on another laptop)
Can anyone give me a suggestion. I have not found 5830 specific USB drivers for example (nor do I know if they even exist). Any help is appreciated!
Regards,
Roel

SOLVED...sort of...
I used a workaround. I used a Windows 7 computer and there it worked perfect.
roel1976 said:
Hello all,
I got an old 5830 Galaxy Ace I wanna hand over to a friend. I want to flash stock ROM onto it.
When I start the phone normally I can connect via USB cable and see the files on the device.
However when entering 'downloading' mode (power+volume down+home) I get the error: This device cannot start. (Code 10) "A request for the USB BOS descriptor failed." (copied from Device Manager properties of Samsung USB Composite Device). I also see this ballon pop in in the sys tray
The device does NOT show up in either Odin or Flashtool.
I am on Win 8.1 64bit laptop. I have searched and trawled the internet already and did the following:
- disabled signature verification in startup options of windows
- installed fastboot drivers via flashtool
- installed Samsung USB drivers
- tried 4 different USB ports and two different cables (and also on another laptop)
Can anyone give me a suggestion. I have not found 5830 specific USB drivers for example (nor do I know if they even exist). Any help is appreciated!
Regards,
Roel
Click to expand...
Click to collapse

hi, i had same USB problem, windows7 worked for this old phone

MTP Device not working

I can connect ADB but file transfer is not working when I try to update Unknown devices in device Manager I got MTP Device A service installation section in this INF is invalid. on the phone usb connection is set to MTP.
I tried this https://www.tenforums.com/drivers-h...r1-hd-phone-usb-connectito-windows-10-pc.html but no luck except I got also update Unknown devices in potable devices. I am sure this was working in the past.
so where are the latest drivers for it?

guliver365 said:
I can connect ADB but file transfer is not working when I try to update Unknown devices in device Manager I got MTP Device A service installation section in this INF is invalid. on the phone usb connection is set to MTP.
I tried this https://www.tenforums.com/drivers-h...r1-hd-phone-usb-connectito-windows-10-pc.html but no luck except I got also update Unknown devices in potable devices. I am sure this was working in the past.
so where are the latest drivers for it?
Click to expand...
Click to collapse
I have this problem all the time. I only have a work around. Eventually it always comes back. Anyway, in device manager I select update driver, browse my computer for driver, let me pick from a list, scroll to portable devices , click next, choose MTP USB Device

I have done it before doing the https://www.tenforums.com/drivers-ha...ows-10-pc.html it was not working but now it shows the R1 HD
Thank you

Can't Use USB File Transfer - Android Driver indicates failure

Hi - For a long time, my OP3T worked fine when I would connect the USB to do file transfers.
However, for a few weeks now, USB File Transfer stopped working. on my home PC. I know that there must be some issue with my PC because USB File Transfer works fine with my Win10 work PC.
PTP transfer seems to work OK on the Home PC. When I look at the Other Devices >> Android in Win10 Device Manager, there is a exclamation point indicating a driver failure. I have tried installing/reinstalling the official OnePlus USB drivers, but no luck.
Can anyone help?
Thanks,
¿GJ?

Try this:
https://www.howtogeek.com/195607/ho...evice-to-show-up-in-file-explorer-if-it-isnt/
If that's no help try the Google USB Drivers:
https://developer.android.com/studio/run/win-usb

Question [SOLVED] ADB/Fastboot doesn't see phone

I'm running an older version of OMNIROM with Microg on my Zenfone 8 (US). Obviously, the bootloader is unlocked. I've got TWRP on it also. A few days ago I had a problem where the cell service just died. I couldn't enable Mobile Data and had a little x over the cell signal bars. I finally got the cell service working by wiping Dalvik Cache, Data, and internal storage. However, since I just wiped my phone, I'd like to update it to Android 12 (either OMNIROM or LineageOS). However, my Windown 10 PC does not see the phone when I try to use ADB or Fastboot. It doesn't list any device.
Things I've tried:
-In addition to the ASUS cable, tried OnePlus 6's cable
-4 different USB ports on my PC (2.0 and 3.0)
-Numerous ADB drivers, including ASUS' driver, and many generic drivers
-Three different ADB/Fastboot installations
-Ran Windows' device troubleshooter
-Tried installing driver with Windows ignoring driver certificates
I do have USB Debugging enabled. I can see the phone when it is running the ROM and set to File Transfer.
Any suggestions on what I could try to get my phone recognized?

I've been at this most of the day. I post here, then try one more driver change, and it works. Well, it worked enough to get fastboot to recognize it, so I flashed stock.
The driver change I did was to pull up Devices and Printers in Win10. I right-clicked on the Zenfone 8, selected Properties | Hardware. It showed that there was no driver installed for the device. I clicked on Update Driver, and pointed it to the folder with the ASUS official drivers (which I had installed previously in a different manner). I let it do its thing. Rebooted, and it worked. I hope this helps somebody else.

Yippee38 said:
I'm running an older version of OMNIROM with Microg on my Zenfone 8 (US). Obviously, the bootloader is unlocked. I've got TWRP on it also. A few days ago I had a problem where the cell service just died. I couldn't enable Mobile Data and had a little x over the cell signal bars. I finally got the cell service working by wiping Dalvik Cache, Data, and internal storage. However, since I just wiped my phone, I'd like to update it to Android 12 (either OMNIROM or LineageOS). However, my Windown 10 PC does not see the phone when I try to use ADB or Fastboot. It doesn't list any device.
Things I've tried:
-In addition to the ASUS cable, tried OnePlus 6's cable
-4 different USB ports on my PC (2.0 and 3.0)
-Numerous ADB drivers, including ASUS' driver, and many generic drivers
-Three different ADB/Fastboot installations
-Ran Windows' device troubleshooter
-Tried installing driver with Windows ignoring driver certificates
I do have USB Debugging enabled. I can see the phone when it is running the ROM and set to File Transfer.
Any suggestions on what I could try to get my phone recognized?
Click to expand...
Click to collapse
Any change to try Linux on your PC ? e.g. via LIveCD or in a virtual machine with access to the USB port?

bnsmb said:
Any change to try Linux on your PC ? e.g. via LIveCD or in a virtual machine with access to the USB port?
Click to expand...
Click to collapse
I could try it on my laptop which only runs linux, but at this point, I'm past that, so I really don't need to go back and try it again.