Related
Hi,
i have big problem with the USB Debug and ADB on my pc.
Everytime i stuck the usb of my g1 in my pc the internet stop working and seconds later i become bluescreen...
WORKER_THREAD_RETURNED_AT_BAD_IRQL...
Problem with NDIS.sys...
I use Fritz Wlan USB Stick for Internet Connection... without plugged in W-lan usb stick it fully work....
What can i do for fix this problem and use G1 and ADB...
Other question:
How do i delete actual undeletable Apps like mp3-downloads, google talk etc.???
Because i heard it's possible with ADB/Terminal Emulator...
ScorqYoN
If you are trying to use ADB just to remove apps, there's way easier ways to do it. You wont even need Terminal either.
Just hit up the market and search "su file browser" or "root explorer". These apps will cost you though. Su file browser is best by far. (pm me if u need help finding app)
all you have to do is navigate to system/app.
Click the "S" icon which will make your system folder read/write
Delete any apps you dont want in there.
Clear your Dalvik Cache and reboot. (optional)
Asa far as ADB and a USB Internet stick, i have no idea. Probably the USB port you set up ADB on is the USB port you're using for the Internet stick? ADB is causing a conflict somewhere. Are you using windows7? Theres a special way to set up ADB on 7, google it. It involves installing HTC device center i think (did it a while ago). Good luck.
Deleted response
But with your procedure I can delete all that is listed under Applications???
Can i do this with ASTRO, too???
I'm using XP...
I need ADB for many things...
The strange thing is, when my G1 is connect with PC, it won't detect other later plugged usb devices, like usb storage etc...
And their is a unknown device, which can't find a driver...
Please help!
The error (Bluescreen: WORKER_THREAD_RETURNED_AT_BAD_IRQL... NDIS.sys) also come when I connect the G1 without USB Debugging with the PC after few moment...
Wheres the problem...
With an other Notebook i also have configured ADB and it works super with W-Lan(Onboard) and Lan (Onboard).
More Information:
My MoBo: aBit AB9 Pro
I use everest ultimate and tuneup
Windows XP PRO SP3
?????????????????????????
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Uninstall the usb drivers. Not sure what there called when kies installs it
fivebraids said:
Well, I spent the last week or so having all sorts of creative fun with my new Captivate. Unfortunately, I was having the random shutdown issue, so I decided to remove SRE, SU, etc, using ODIN to restore my phone back to stock and get it exchanged for a new one.
I came home with my new phone today and proceeded to start the customization process all over. Before I did anything serious, I connected my new Captivate to my desktop, to both charge the battery and to sync with outlook using Kies.
With a full battery and my contacts loaded, I moved on the rooting and installing SRE. I then installed a bunch of apps, including ADW, ShopSavvy, and a bunch of games.
I then tried to get on the Market to download a few more apps. I forgot to 'emulate' T-Mobile to get around the AT&T censorship, so I fired up MarketAccess. I got an error message saying that MarketAccess couldn't get SU privs. That made no sense, since the phone was rooted, and SRE installed SuperUser. I downloaded the latest copy of Superuser and installed that. The SU problem was now fixed. (Turns out there was a glitch in the SRE I used. Designgears quickly fixed the zip file, but I was already using the glitchy one.)
Anyway, after loading a slew of apps/games, I plugged the phone back into the desktop to charge the battery some more. I got two error messages, one on the phone, and one on the desktop.
The phone complained that it was not on an 'idle' screen, since ADW was running. Since I had set ADW to be the default launcher, I used TitaniumBackup to temporarily uninstall ADW. (I couldn't figure out how to stop ADW and set TW back to the default.)
The desktop is more or a serious problem. I am now getting an info bubble saying that the USB DEVICE IS NOT RECOGNIZED.
The correct USB drivers are installed. I've used them to ODIN my previous phone back to stock. And they were working fine before I added SRE, ADW, etc.
I've uninstalled and reinstalled the drivers. Didn't help.
I tried USB Debugging, on and off. Didn't help.
I tried the age-old trick of unplugging the desktop and leaving it unplugged for 30 minutes. Didn't help.
So, here are my questions:
1) Does anyone know how to correct the DEVICE NOT RECOGNIZED error?
2) If not, is there anyway for me to restore the phone to stock without USB connectivity?
The phone still functions fine, just no USB. I was able to download the new SRE (with SuperUser fixed) using Dolphin browser. I then used My Files to rename and move the zip file to the root directory, and was able to install it fine. Is this same approach possible to restore to stock?
Thanks in advance...
Click to expand...
Click to collapse
I had a similar problem and it turn out that Kies hosed up all my drivers...The only way I got it fix was by totally removing any trace of Kies and then uninstalled all my samsung drivers and usb drivers and then rebooted my pc. Then I reinstalled the samsung drivers and win 7 did the rest...
Well, I haven't uninstalled Kies yet. Although I have uninstalled and reinstalled the drivers from the ODIN thread. No difference.
I even uninstalled the ODIN referred drivers and tried the drivers directly from the Samsung site. Still no difference.
I'll go ahead and try uninstalling Kies and then the ODIN drivers, reinstall the ODIN drivers and see if that helps.
I've also ordered a new cable, since I've read a few threads on other forums where the problem was bad cables. I was going to go to AT&T and get a new cable, but they want $24.99. I just ordered a pair from Amazon at $3.99 each, with free shipping!!
Thanks...off to try ridding myself of Kies...
Well, deleting Kies (and associated drivers) didn't help!
After deleting Kies, I tried both the ODIN referenced drivers, as well as those from the Samsung site. Still not working!
I guess I'll wait on a new cable and see if that helps...
Okay, I think I'm in BIG TROUBLE here!!!
New cables arrived today, but they made no difference at all! Still getting the USB Device Not Recognized message. Doesn't matter if I plug the cable in while the phone is on and select any of the connection options (Kies, Mass Storage, etc.). It gives me the same message when I have Odin running and plug the phone in while holding the volume keys.
To further add to the problem, I tried installing the Odin referenced USB drivers on my wife's laptop which has never seen this phone or Kies. SAME PROBLEM!
I'm thinking there might actually be something wrong with the physical port on the phone. But this highlights my actual problem...
How can I return the phone (for the second time) when this phone has been rooted and is running SRE 1.2.1a ?!?!?
Apparently, there's no way for me to restore this thing to stock without USB.
Any ideas/suggestions?
Relax dude--I just got a captivate a few weeks ago, and have it working on tmobile.
For the drivers, when you plug your phone in, you're getting some errors. I know you uninstalled the drivers, but to double-check, open up device manager and see if there are any ! marks for the phone. Right-click and uninstall the entries. Also, you might try using a different USB port. I can only get my phone to connect using one of the 6 usb ports i've tried. Finally, and I don't know if these are the drivers for Odin, but I downloaded these drivers: SGH-i897_Captivate_USB_Drivers_5_02_0_2
When the phone connects, you might want to go to device manager, find the device(s), righ-click and and select 'update driver'. then, in the driver update window, pick 'manual' or 'let me specify location' and navigate to the unzipped SGH-i897_Captivate_USB_Drivers_5_02_0_2 file. Then, it should work.
Like I said, I have no idea if those are the drivers for odin...but I'm about to find out
I'd like to relax, but I think I'm dealing with a phone with a bad usb port...and since I've rooted, SRE'ed, etc., I won't be able to return it.
Anyway...
The driver you're using is the 'direct from Samsung' version, not the one for Odin.
Regardless, I've been through the exercise you propose...both with the Samsung and Odin drivers. When you attempt to manually install drivers, you need to point the installer to the ".inf" setup information file to use. The Samsung driver has three: SSADADB2.inf, SSADBUS.inf, and SSADMDM2.inf.
I get the following message when trying to use any of these three setup files:
The specified location does not contain information about your hardware.
Oh, and I've tried several different USB ports on the computer...both on my external hub and directly into the back of the machine.
Thanks for the suggestions, but still not working...
I'm really thinking I have a bad port on the phone...especially since trying the connection on my wife's laptop produces the exact same error.
Dam...
Still trying to find a way to restore the phone to stock without a USB connection...
i also have this "DEVICE NOT RECOGNIZED" on my sony x1.
Drivers
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
superdog404 said:
I was having trouble using the USB drivers from Samsung the one's you were using SGH-i897_Captivate_USB_Drivers_5_02_0_2. The computer didn't recognize the phone. If you havn't tryed these already give these a try. Well since I am new I can't post the url. Put these words together (forum.xda-developers com archive index.php t-730638)
Click to expand...
Click to collapse
Not sure different USB drivers would help, but I went to the thread you show and tried to download the 32bit drivers. This is what I get:
{"error": "Invalid access attempt for this token"}
Oh well, thanks anyway.
I'm still thinking that the problem is hardware on the phone. I've tried four different cables, and three different computers. All show same problem of DEVICE NOT RECOGNIZED.
Still trying to figure out how to restore to stock without USB connection for ODIN so I can exchange for a new phone...
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
No modifications, same error
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
mukherji said:
I didn't make any modifications to my new AT&T Captivate, and I too am getting USB Device not recognized under any of the following conditions:
- drivers installed, no Kies
- drivers installed after Kies
- Kies installed after drivers
No response to any USB connection mode (Kies, mass storage, media player, PC INternet).
Only way to exchange files is to physically remove the SD card and plug it into my PC. Windows XP Professional.
By the way, which of the three drivers is the correct one: ssadadb2.inf, ssadbus.inf, or ssadmdm2.inf? Pardon my ignorance as to how this is supposed to work.
Click to expand...
Click to collapse
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Rhiannon224 said:
You should return your phone if it's new if you can't get your computer to recognize it when you have the correct settings and drivers.
Choose, mass storage. I use the drivers from ODIN, I also have to ones from Samsung's site but they are for Windows 7 64bit. Before you plug any Captivate into a PC for the first time you need to first change the settings to USB Mass storage or Kies will attemp to download drivers. Once you get your phone to mass storage windows should find the drivers. I am not sure, I am running Windows 7, I have an old desktop that runs XP, I could plug my phone in and check for you.
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
JayPhill89 said:
What are your USB settings on the device? Do you have debug mode enabled or maybe you've set the device to connect to kies right away which is producing errors on your PC. What versions of windows have you been trying to connect to? This sounds like a windows problem more than anything else.
Click to expand...
Click to collapse
USB is set to Ask on connection
Debug off or on makes no difference
All tests have been done on XP machines (3 different ones)
I'm all but positive this is hardware...
Thanks for trying to help!
Rhiannon224 said:
<snip>
FiveBraids
Settings--developement-- check debugging mode, this will allow you to open a command shell. Using SDK and ADB commands.
Download SDK online.
http://developer.android.com/sdk/index.html
Follow the installation instructions. This will allow you to use the command ADB download to get your phone into download mode. Kies screws my drivers so I don't use it.
Click to expand...
Click to collapse
I haven't tried ADB, but I'm not understanding how ADB would be able to connect when the connection to the computer is failing at the driver level. I guess I can give it a try tomorrow.
Thanks for trying to help!
What would REALLY help me is for someone to post a backup taken of a completely stock (ODIN'ed) phone using ROM manager. I'm thinking I could load that on the phone and then be able to return it for a new phone!
Any volunteers...please?
techmik67 said:
The 2 folders I found that have the drivers are /program files/android/, .... and /program files/samsung. Delete these subfolders that have drivers in them.
Download this : http://www.megaupload.com/?d=N4GC49JL and unzip. In the folders inside (i386 and amd) there are uninstallers. Run whichever version is appropriate for you. If you have no drivers or it doesn't say to reboot, the main folder has a setup program. Run that to install the proper drivers. When you plug in to usb, it will now find these drivers.
Also, for me, ONLY the REAR usb ports work properly with this. Top, front, and ext hub ALL give issues.....
Click to expand...
Click to collapse
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
jaxf250 said:
Big thanks!
Just got my first Android device a couple hours ago (went from ATT Bold to Captivate), and could not get the phone to mount to my PC.... followed your instructions here and BAM! Perfect-o! I have now rooted....
OK, not sure where to go next... was thinking about just getting a new ROM flashed since I am totally stock at this point.... the fun begins!!!
Click to expand...
Click to collapse
Great!! Glad it all worked for you. My next advice is, before adding anything READ A LOT!!! =) Decide what you want from the descriptions and issues you will see in the threads....
Happy modding!!
I didn't see, I just skimmed through bit did you try to put the phone in download mode and see if windows sees that (different drivers come in to play in download mode and none of the touch wiz stuff is running)? it would test the idea of a bad port.
then you can still always install linux and use adw from there, linux and macs don't need drivers. if that doesn't work, put insurance on the phone if you haven't already then drop it in the sink and get another one.
also I think although I don't know but I think adw may have something to do with it. and incorrectly uninstalling it. first put the phone in download mode then you can work from there on ways to fix that.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Ok, I've given up trying to get this to work. I'm 100% convinced this is a hardware problem with the phone!
I had another thread going, looking for a way to restore this phone (remove SRE, SU, etc.) without usb/ODIN so I could return it to AT&T. I've figured out how to restore it to stock and will be heading to AT&T in the morning.
Thanks to everyone for their patience and assistance!
Hey, everyone, I tried posting about this in the CM7 general discussion thread, but no one seemed apt to respond.
I think this was a problem that popped up in the 60s or 70s in terms of nightlies, but I'm having it again now since around the 155 mark.
I'm on 160 and when I plug my NC into the USB cable, I no longer get any options to connect for file transfers in the notification area. If anyone could help me out with this, I'd really appreciate it. It's just so perplexing and no one seems be having this issue except me. If it's user-side error, that's fine as well, I'd just like to know how to fix it.
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
votinh said:
1. When you plugged the NC in, did the PC recognize any "removable" drive?
2. In the notification area, did you see any other indication?
3. You run CM7 off uSD or eMMC?
Click to expand...
Click to collapse
1. No, nothing comes up.
2. The notification area remains blank.
3. I'm running it off eMMC.
Thanks for taking the time, by the way!
If so, unplug the usb cable then replug in a few times and see what happens.
If still nothing, try to use other usb cable.
Oh, btw, have you had Nookcolotweaks app installed?
I do have Nook Tweaks installed, yes. I'm using the cable that came with the Nook, but I'm not sure I have any other cables around.
Do make sure you check OFF the USB Host feature (reboot and reconnect)
I gave that a try, too, but still nothing. So confusing!
Don't be so hard on yourself.
Let try it on different computer if you have.
Also try difference usb cable.
Last, if nothing works, update latest nightly build
When you disconnect and reconnect the nook in testing/trying to get it recognized... unplug usb cable from computer... its made a difference at times.
I know this sounds basic but in applications-settings ensure you have usb debugging checked. Sometimes when flashing different nightlies, settings change.
Sent from my NookColor using Tapatalk
Thanks again for all the help, everyone! I made sure USB debugging was checked and tried unplugging/replugging the cable, but there's still no notification coming up.
A new development:
I tried connecting it to my Windows PC instead of my Linux and it brought up this message that said it didn't recognize the device. I also tried to get ADB to see it and it can't. Does this information help or am I in trouble here?
Next time, do clearly indicate that you are using Linux or Windows. I'm sure many members here are Linux but still far less support than Windows world.
When I provided those suggestions in previous posts, I meant in Windows.
Anyway, back to your issue.
1. "it didn't recognize the device" because of missing adb usb driver. You need to get it installed first in order to use ADB, however it has nothing to do with your usb mass storage function. For now, you don't need to worry about it just yet.
2. Back to my question before, have you seen any "removable" on the PC (Windows)
Along with USB Host uncheck, if still having problem, I would suggest you either downgrade to the earlier versions or wait until tomorrow and update with another nightly build.
Good luck
I have the ADB drivers installed in Windows, as far as I know. I've used it before.
I typed "adb devices" into the prompt and it doesn't see the NC at all. Since one of the nightlies seems to be what prompted this sudden change in connectivity, I guess I'll just hope that one of the new ones can fix it. Thanks again.
Also, Windows doesn't show anything "removable" except for my external HD.
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
arda99 said:
Try to disable usb debugging as you can still use ADB over wifi. This should always put the device to usb storage mode when connected.
Click to expand...
Click to collapse
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
junkrobot said:
I tried this out and even ADB wireless can't connect to my device. I even re-installed the ADB drivers in Windows to be sure the problem wasn't on that end.
Click to expand...
Click to collapse
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
If you've installed ADB drivers, you might want to remove it as this might mess up usb storage.
arda99 said:
If you're using ADB wireless, no need to install any driver on Windows PC, you just need 2 files: adb.exe and AdbWinApi.dll, to connect to Android device.
Click to expand...
Click to collapse
Alrighty. I have those two. I've connected my NC to ADB both wirelessly and and with the cable in the past, so this should all be straightforward anyhow. It just plain refuses to cooperate.
Go to the Marketplace and download "Nook Color UMS" app. Follow instructions and it will mount properly. I had the same issue used it and it mounts proper through the app.
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.
Hey guys, run into a little problem recently. I am having trouble with file transfers via USB.
I can transfer/copy files from the phone to my pc without problems, so i know storage is accessible, BUT i cant transfer files to the phone from the pc, it give an error: device disconnected or something like that... Any ideas how i can solve this or what the issue may be? I used airdroid to transfer some files and it worked without a problem. I thought it could be USB problem, but since transfer from phone is working... and storage is not broken or unaccessible cause i can copy files with airdroid and i can also see files when i connect it to pc through USB.
As an extra piece of info (if they are related), i was trying to push the files through adb and it gave me an error:closed...and trying to mount sdcard from recovery didnt work...
Any help/solutions welcome!!
Thanks!!
Coldsun15
PD: im running trickdroid (version 5 or something like that...yeah, i gotta update hehehehe)
Not S-off nor superCID
mh doesnt sound good :/ maybe reformat? Have you tried another PC?
I never had problems with Win7 64 detect and transfer to and from the mtp partition, however had some problems with adb. you can always try clean reinstalling the HTC usb drivers, that helped here. as suggested above try other pc or different os, otherwise you might try to change roms or clean reinstall same or other rom.. hth
Sent from my HTC One using Tapatalk 4