Related
Hey guys,
For some reason, my Windows 7 32bit laptop is not recognizing the Galaxy tab at all when in download mode. I have installed kies (which incidentally also doesn't recognize the tab), and installed the individual drivers, but cannot get my computer to even see the Tab.
When the Tab is in normal mode (debugging turned off), I can mount the Tab as a drive and it has no problems.
Has anybody else run into this issue? The Tab is not showing up in the device manager at all. I do have root, and my end desire is to connect with Heimdall, and continue to get the error message "Failed to detect compatible device."
Any help would be greatly appreciated.
Seth
Download and install drivers for your tab. Samsung website should have them, if not they shouldn't be too hard to find.
drivers
Hi,
Already tried that. Kies doesn't recognize the device at all (with USB debugging active and not active both), and the Device Manager doesn't show anything either. When I plug the tab in, it recognizes that it is connected, but mounting the SD card as a drive doesn't do anything either.
The worst part about it is that I'm not sure that I can even revert to stock without being able to get Heimdall working. I've searched a ton, and it seems to be the key to just about everything. Any other ideas?
Seth
have you tried to install the drivers that come with Heimdall? I've had to force install those a couple times to get my Tab recognized in download mode.
Heimdall drivers
pvtjoker42,
Can you explain a little about what you mean? I am running Heimdall 1.1.1 have done the following:
1. Browse from the main folder to the "Drivers" folder and run zadig as an Administrator.
2. Click on "Options" and select "List all devices"
3. Click on the dropdown menu and search for anything that might be related to Samsung Galaxy Tab or Android of which there are none.
Is there a different way to force the install of the Heimdall drivers that I'm unaware of?
Thanks for your help,
Seth
when you drop down the list of devices what all is listed? I've had it show up as just a serial device before, with no mention of samsung/tab/galaxy etc..
Devices
Cisco VT Camera II (Interface 0)
Cisco Microphone (VT Camera II) (Interface 2)
USB Receiver (Interface 0)
USB Receiver (Interface 1)
USB-Serial Controller D
Fingerprint Sensor
Optical Drive Controller
TOSHIBA Web Camera (Interface 0)
USB Multimedia Audio Device (Interface 0)
USB Multimedia Audio Device (Interface 3)
Those same entries can be found in Device Manager>Universal Serial Bus controllers even on first boot if the Tab is not connected. Even after connecting the Tab, this list does not change.
Thanks again for your help!
Seth
have you tried uninstalling everything related to the tab? Kies, the specific drivers etc, then trying the Heimdall drivers?
So all the devices listed above are there when the Tab isn't even plugged in? Odd.. I would have suggested trying it for the USB-Serial Controller D, but if it's there without the Tab plugged in it sound like a different system device.
Don't suppose you have access to a different pc to try it on? see if it even notices the Tab being plugged in and tries to install drivers..
Yeah, I have other computers to try. Tried plugging it in yesterday to a different computer (same brand and model) with no change. Computer didn't recognize the device at all and/or try to install drivers.
Usually when an unknown device is plugged into a computer, the computer registers that it's there - the Device Manager shows an "Unknown Device" somewhere in the list, but this isn't the case with this device. Not sure what happened, but it appears as though I goofed up the USB somehow in the rooting process or the port itself went bad.
I'll try other computers and write back.
Thanks again,
Seth
I've tried three different computers with the same outcome. They do not register the device at all, and I cannot mount the SD card to the computer. I'm definitely at a bit of a loss at this point. Without USB, I'm not sure how else to make this happen. Ideas?
Seth
Just to double check with hemidall ur opening the drivers folder and running zadig.exe in there going to options>list all devices
Yes, that is correct. I'm opening the Heimdall 1.1.1 folder, opening the drivers folder, and running zadig. Nothing pops up at all and nothing shows up in the device manager.
I cannot mount the SD card to my computer, but the Tab recognizes it when I plug it into the computer's USB port. That's as far as I can get, however, as the computer does not see the Tab at all.
Have you tried 'fix permisions' in recovery mode - usually under the advanced option?
Sent from my GT-P1000 using XDA App
There is no "Fix permissions" in this recovery mode. Tried to fix permissions from cwr (which only went through 2 lines), but it doesn't seem to make any difference. Still force closes Gallery when I try to mount the SD card. Also force closes gallery when I try to open gallery.
This is very strange. It continues to tell me that there is an update available. I might go ahead and take it to see if it takes me back to stock. I would be okay with this as long as I had USB connectivity again and could root.
Any other thoughts?
Seth
P.S. Tried to take the update, but it gets about 1/3 of the way through the install and fails.
Any other ideas on how to flash without Heimdall?
Seth, what about trying Odin3 and its drivers?
Sent from my GT-P1000 using XDA App
I'll look around and find Odin3 and give it a shot. I'm concerned that because my computer doesn't recognize it as a connected USB device, that no program will see it either. That said, it's worth the shot and I appreciate the suggestion.
Do you know whether I can use the same files for Odin that I would use with Heimdall? Do they need to be packaged differently?
Thanks in advance,
Seth
If you have GSM based tab you can try flashing Team Overcome's Kratos ROM (I had no issues with download mode following their excellent ROM flashing instruction here http://p1000.teamovercome.net/?page_id=64 ) which involves download mode + using Odin, which displayed that it's connected to a tab through a serial port emulation. At least you can confirm if your tab's download mode is working. I'm using Win 7 Home Premium 64 btw.
I downloaded Odin 3, but without knowing if I am able to flash a package designed for Heimdall, I'm not sure what Odin 3 would tell me. Thoughts? Can I use Odin3 to transfer one of the Heimdall-specific ROMs to the Tab?
I had this same problem some weeks back. I had to use the drivers that came with Heimdall, and most importantly, in order to get it to recognize in download mode, I had to install them while in download mode and plugged in.
Preface:
I was performing a nandroid restore and then accidentally removed the battery at some point.
Situation:
Phone does not boot past black and white galaxy S screen.
Going into Clockwork Recovery, I am unable to factory reset, or start a restore because it seemingly is not able to detect any of the storage of the device....
(sample messages below):
Code:
E:unknown volume for path [/data]
E:unknown volume for path [/cache]
E:unknown volume for path [/sdcard]
E:unknown volume "/data"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
Furthermore, I can't just re-flash in download mode because the computer refuses to detect it in windows. At first I thought it was a driver problem, because i've had difficulty with my computer detecting the phone at times, but now I suspect download mode is broken somehow (after trying to reinstall the drivers and installing kies, and various combinations therein). When the phone is plugged into a different computer ( laptop ) running linux, I get messages like these on the command line:
Code:
usb 1-1: device not accepting address 2, error -71
usb 1-1: device descriptor read/64, error -71
usb 1-1: device descriptor read/8, error -71
hub-1.0:1.0: unable to enumerate USB device on port 1
On another note assuming I can't resolve this in a more delicate manner, can someone tell me if it is possible to use a jtag programmer to flash the phone?
Would using a jig to get into download mode make a difference?
Thank you very much for your assistance.
Wich Rom where you trying to restore to?
and what Rom were you on before you hit the Restore button?
pzayx said:
Wich Rom where you trying to restore to?
and what Rom were you on before you hit the Restore button?
Click to expand...
Click to collapse
I was trying to restore to stock JVR (rooted, no lagfix, semaphore kernel I think), from the ice cream sandwich port.
okey, i see, you might need to download android sdk and download the latest usb package or search around for the drivers for Nexus, since the usb drivers for galaxy s doesnt work with cm7/ics builds.
if you manage to make your pc recognise your phone you could check out this thread:
http://forum.xda-developers.com/showthread.php?t=1134975
btw, if you want to restore from ICS to stock gingerbread i think you will have to install a stock gingerbread ROM before you restore.
Hope this helps you!
(edit: if you find the driver or download it from SDK you can head here http://www.dkszone.net/setup-install-adb-android-debug-bridge-windows-7 to see a guide for how to set the driver manually)
Hm, Well I had already had the SDK and the drivers on my computer, but do I need to do anything special to install them? I recall previously trying the [right-click inf > Install] method, for some reason, but that didn't work
zeco said:
Hm, Well I had already had the SDK and the drivers on my computer, but do I need to do anything special to install them? I recall previously trying the [right-click inf > Install] method, for some reason, but that didn't work
Click to expand...
Click to collapse
i had to manually set the drivers,
i used this thread to do it:
http://www.dkszone.net/setup-install-adb-android-debug-bridge-windows-7
Just jump straight to step #7 if you have the drivers
Upon selecting the driver, windows immediately complains:
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems."
Agh, And I thought this might actually work too.
EDIT:
Unknown if this is a success or not... but i've been alternating computers trying various permutations of fixes, and this time my laptop actually says the word samsung in the device manager....
EDIT2: Odin Sees it! I am going to try to flash JVR now... then retry restore from there....
P.S. I hope to god this is not related, but I actually just dropped my phone in between switching to attempt on laptop....
EDIT3: Detection, but immediate failure open attempting to flash. Then rebooted phone and now upon pressing start again it seems to be flashing.........
P.P.S: I've got to say, the most stable thing about this series of phone has got to be the bootloaders :#, Like seriously, this thing is boss.
EDIT4: Well. Managed to flash, Now I just get stock recovery with the same problem of it not finding the storage... I guess I will try flashing with repartion and a PIT?
I had to manually choose the folder where i store the Android SDK.
like c:\sdk\sdk\
it sucks when things dosent work like they should do!
So Yeah... Despite not really changing very much at all, download mode connects, and My phone now boots, Which is a lot better than where I was at previously So thanks for your help.
yw, happy i could help you!
The next mystery to solve is why Recovery is still screwed, and why I can boot my device anyway....
Hmm
So youre still getting the E:\ unknown volume *****?
Wich odin version do u use?
I had to use Ezodin last time to get it to flash,
then i flashed full stock JVH (with pda, phone & csc)
but i guess you could try to flash a stock Gingerbread bootloader too,
http://forum.xda-developers.com/showthread.php?t=1089989 Here is both Froyo and Gingerbread bootloaders.
And i have Atached EZodin for you.
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
Hi everybody I`d appreciate a lot if you provide me with any sort of help. The problem is following: while I was flashing a new rom my phone went out of power. After reboot I received a continuous loop of boot screen=>install screen=>reboot. In recovery mode when I try to choose the rom`s zip file I have no options. It says "No files found". I tried to mount sdcard and as far as I can see there was no failures. However, mounting emmc results in error. Equally, I tried to connect via Odin, but it does not recognize the device. Please,help me to get at least to the flashing point.
Keswick said:
Hi everybody I`d appreciate a lot if you provide me with any sort of help. The problem is following: while I was flashing a new rom my phone went out of power. After reboot I received a continuous loop of boot screen=>install screen=>reboot. In recovery mode when I try to choose the rom`s zip file I have no options. It says "No files found". I tried to mount sdcard and as far as I can see there was no failures. However, mounting emmc results in error. Equally, I tried to connect via Odin, but it does not recognize the device. Please,help me to get at least to the flashing point.
Click to expand...
Click to collapse
just mount phone under USB storage and copy the ROM files to the SD card that can be read by your phone and Flash the ROM from that location in CWM . To fix USB connections problems, read this
Check this out! You , YES! you are an " Android ". Not your phone but U.
Thank you for the quick answer. I tried to mount it under USB storage however my computer did not recognize the phone. Following your advice I started to check the connection. The main obstacle was indeed in that Odin was not able to recognize the device under Windows 8.1. After installation of Samsung USB Driver v.1.5.25.0-retail I managed to re-flash my device smoothly.
Keswick said:
Thank you for the quick answer. I tried to mount it under USB storage however my computer did not recognize the phone. Following your advice I started to check the connection. The main obstacle was indeed in that Odin was not able to recognize the device under Windows 8.1. After installation of Samsung USB Driver v.1.5.25.0-retail I managed to re-flash my device smoothly.
Click to expand...
Click to collapse
When your problem has been solved, EDIT your first post and remove [Q][Help] and add [Solved]
This will help others in their search and ensure that you don't need help anymore.
Check this out! You , YES! you are an " Android ". Not your phone but U.
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