There are alot of things that are different compared to htc devices so far.
Now I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1285894
Downloaded and installed kies drivers, Downloaded odin, downloaded and loaded codeworkx, used superoneclick..it all went smooth. I tried different roms through cwm. Currently I'm running cm7 as I am so used to it. But here is my question, on two different pc's when I tried to run "adb devices" it cannot find my device. I wanted to push something and couldnt find my devices. I have the Superuser icon in my apps. Also when I tried to su in terminal app it said permission denied. I'm a bit baffled lol. All my drivers seemed to have installed fine.
SysAdmNj said:
There are alot of things that are different compared to htc devices so far.
Now I rooted using this method:
http://forum.xda-developers.com/showthread.php?t=1285894
Downloaded and installed kies drivers, Downloaded odin, downloaded and loaded codeworkx, used superoneclick..it all went smooth. I tried different roms through cwm. Currently I'm running cm7 as I am so used to it. But here is my question, on two different pc's when I tried to run "adb devices" it cannot find my device. I wanted to push something and couldnt find my devices. I have the Superuser icon in my apps. Also when I tried to su in terminal app it said permission denied. I'm a bit baffled lol. All my drivers seemed to have installed fine.
Click to expand...
Click to collapse
If "adb devices" failed you either have a driver problem or USB debugging is turned off
I do recall that with recent CM7 builds on my Infuse, root didn't work on first boot. I had to open the Superuser app or reboot, not sure which one fixed the problem.
Entropy512 said:
If "adb devices" failed you either have a driver problem or USB debugging is turned off
I do recall that with recent CM7 builds on my Infuse, root didn't work on first boot. I had to open the Superuser app or reboot, not sure which one fixed the problem.
Click to expand...
Click to collapse
usb debugging has been on. This issue I mention happened when I was stock, after I tried cognition, and now using cm7. Might be a driver issue, is there any other samsung drivers I can try for my windows machines?
SysAdmNj said:
usb debugging has been on. This issue I mention happened when I was stock, after I tried cognition, and now using cm7. Might be a driver issue, is there any other samsung drivers I can try for my windows machines?
Click to expand...
Click to collapse
if you are on CM7, i think you need to install the nexus S drivers, which are included in the Android SDK. you will need to run the emulator and run the update in SDK
Since you mentioned this has happened on two different computers, I doubt my advice will help. With that said, whenever I've had issues like this, I've found that USB ports tend to be the culprit. Have you been using ports on the front of a tower? Have you tried the ones on the back as well? Again, just taking a shot at a possible fix...
Related
Hey, I've tried various methods of rooting my GSM Hero, and eventually found the method on this site entitled "VillainROM Roots 2.1 RUU for GSM Hero (Confirmed)". I got as far as trying to run runindos.bat, and this just returns the error as explained. If I run "adb devices" I get "List of devices attatched" and then just nothing after it. Strange.
Does it have anything to do with the fact that HTC Sync never picks up my phone?
Windows 7 64-bit
HTC GSM Hero
3 UK
Android 2.1
adb, drivers or usb debugging, check it
Sent from my HTC Hero using Tapatalk
USB Debugging is enabled, not sure how to check adb but what's the correct way to install the drivers? Is it by running the "SDK Manager" program in my SDK folder?
Moved to Q&A as not development.
Get the drivers via the sdk manager, and manually install them via device manager for the device.
Ahh, sorry about the wrong section. I assumed that Development would be things concerning roots.
SDK Manager only seems to let me install "SDK Platform Android X.X", I don't see any driver installations. Also, I'm not sure where it installs these to.
Edit:
Okay I tried to install "USB Driver" but Windows said that it was already up to date. Still not appearing in adb :/.
Hmmm. Search for drivers in dev forum, as I think I posted mine (or instructions to hack them) on one of the Froyd villain threads somewhere.
Also, I presume you have rebooted and tried adb right after reboot
Drivers for you
Thanks to you both, I'll try those later on today.
I'd rebooted both the PC and the phone and tried it. Nothing unfortunately. It just seems to be a big Windows 7 problem.
I use Win 7 without any problems.
Check out this epic guide by BTDAG,...
http://forum.xda-developers.com/showthread.php?t=776056
Good news and bad news. The drivers are now working, adb is working and runindos.bat is doing it's thing. Unfortunately, when it reboots the second time for recovery, there's just a red triangle with an exclamation mark in it.
I rebooted and got back to where I was, but how do I get the "Care Bear" boot screen? Am I supposed to have moved RA-Hero to my phone first or do I not need anything?
Thanks.
Hi Craig. I had to repeat process 4-5 times before it worked so make sure you have your new rom on SD for when it works. I had all same probs but it will get there. As pulser said on villain try changing directory to avoid echo. It seems to load a little more each time.
Sent from my living room.
Hmm, if the recovery thing with the phone in the background comes up, and has "apply:update.zip" as a selection, should I try that? I've tried a few times and that's usually what comes up, along with reboot phone and another couple of selections.
I've got it! Thanks very much for everything. I just kept doing it and it's working now. I got FroydVillain and I'm loving it! I never realized the Hero could be so smooth.
Also sorry for the double post, I'm used to auto-merging on formus.
When I plug my phone into my computer, it is no longer recognized by windows. It used to... now it doesnt...
I have googled this
I have checked the forums
I have NOT found a solution that works
I have tried booting my phone while it's plugged in.
I have tried reinstalling kies.
The phone comes up as "uknown device" in the usb section of device manager, when i specify the 64bit drivers(I'm running win7 pro 64) it says drivers are up to date! and then proceeds not to work.
I have also tried setting my phone into usb debugging mode.
I have tried all my computers usb ports.
If anyone knows how to help me I'd really appreciate it.... and if I've blindly missed something feel free to call me a moron so long as you successfully help me
chaosthebomb said:
When I plug my phone into my computer, it is no longer recognized by windows. It used to... now it doesnt...
I have googled this
I have checked the forums
I have NOT found a solution that works
I have tried booting my phone while it's plugged in.
I have tried reinstalling kies.
The phone comes up as "uknown device" in the usb section of device manager, when i specify the 64bit drivers(I'm running win7 pro 64) it says drivers are up to date! and then proceeds not to work.
I have also tried setting my phone into usb debugging mode.
I have tried all my computers usb ports.
If anyone knows how to help me I'd really appreciate it.... and if I've blindly missed something feel free to call me a moron so long as you successfully help me
Click to expand...
Click to collapse
Rom? etc.
Sent from my GT-I9000 using XDA Premium App
Stock with a voodoo kernel, do I need to turn voodoo off?
chaosthebomb said:
Stock with a voodoo kernel, do I need to turn voodoo off?
Click to expand...
Click to collapse
I have noticed that some ROM's will enable debugging, I personally run a MAC. But you may want to check those settings to see if its enabled/disabled. But if your charging on it you should be good. Have you tried to odin back to stock and seeing if that helps?
Other thing: do you have the samsung drivers installed on your PC? even if you don't you should still see the external storage just not the internal.
lovemysgs said:
I have noticed that some ROM's will enable debugging, I personally run a MAC. But you may want to check those settings to see if its enabled/disabled. But if your charging on it you should be good. Have you tried to odin back to stock and seeing if that helps?
Other thing: do you have the samsung drivers installed on your PC? even if you don't you should still see the external storage just not the internal.
Click to expand...
Click to collapse
Reinstalk drivers as he said
Sent from my GT-I9000 using XDA Premium App
I should have listed this before... I reinstalled the drivers first before reinstalling kies or checking out device manager
chaosthebomb said:
I should have listed this before... I reinstalled the drivers first before reinstalling kies or checking out device manager
Click to expand...
Click to collapse
Any other devices recognize it?
Sent from my GT-I9000 using XDA Premium App
What rom are you using? If you are running one of the test CM7 builds you have to download the Google drivers from the Android SDK.
Does your phone show up when you mount it as external memory? Did you install the drivers and kies as an administrator?
exact same scenario!
I am having the exact same issues as the OP! Except that i have the unbranded gt-i9000. My galaxy s is completely stock, no custom firmware or launchers. Heck, after the last factory reset, not even any apps!
I have tried every suggestion on every search i could do. I have 4 computers with xp sp3, win7 sp1, ubuntu 10.04.1, and mac os x 10.5.8. Nothing is working on any of them. I've even tried different usb cables, just to rule that out.
Could it be a samsung hardware issue?
So, trying to install the driver exe file from Samsung's website and it won't work. Keeps saying that it failed to install drivers. And, if I have the phone as USB Debugging enabled, it'll pop up with 2 out of 4 that says it failed to install.
My roommate was able to install the .exe file on his Windows 8 beta laptop (I'm running Windows 7 64-bit) without a problem. And, the phone installed fine on his laptop as well. For me, no.
If USB Debugging is not enabled, then yeah, the phone is fine. But, since I want to root this thing, it won't accept the drivers. And, nowhere on Google, searching or Samsung's website provides me any answers whatsoever.
I've done:
Going through regedit and deleting all things Samsung related
Deleted every Samsung folder on my hard drive
Rebooted the computer
Uninstalled the drivers
Reinstalled multiple times
Downloading and installing Kies (did not install any drivers, still failed)
I've done everything I can possibly think of. Couldn't find any answers on here, either. And, doesn't help that the search function is broken.
So, anyone have any idea on how to fix this? And, please do not say "Reinstall Windows" because that's just ridiculous and I shouldn't have to do that for a simple phone driver install. I had my Epic 4G before and that all went smoothly.
Go do something in control panel and uninstall the samsung drivers that you already have on your comp
Then try installing
But I reccomend reinstalling windows
Sent from my SPH-D710 using xda premium
gtuansdiamm said:
Go do something in control panel and uninstall the samsung drivers that you already have on your comp
Then try installing
But I reccomend reinstalling windows
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
+1
I had the same issue with mine on xp. Uninstalled my et4g drivers and installed the gs3 drivers. After a restart, the pc finally recognized my phone as a mass storage.
gtuansdiamm said:
Go do something in control panel and uninstall the samsung drivers that you already have on your comp
Then try installing
Click to expand...
Click to collapse
I already said that I did that.
Volknochi said:
I've done:
Uninstalled the drivers
Reinstalled multiple times
Click to expand...
Click to collapse
And, I'm not reinstalling Windows all over again just for this phone, as I also said. But, it doesn't matter, I already got it rooted through the roommate's laptop.
EDIT: I managed to get it to work. My other half had similar problems with device drivers so just had to have me remove the phone from USB, uninstall driver and then plug the phone back in. And, it actually worked.
I've spent at least 6 hours today trying to figure this out. I've (tried) following numerous guides. I've never used ADB and I am have a lot of trouble with that. I've tried using the one-click tool, that doesnt work. This seems extremely complicated. More complicated than any other phone I've rooted and unlocked. Is it a Windows 8 issue?
I did it, it was a pain however I had other issues with win8 such as all large file downloads would freeze up then my dl speed would skyrocket then appear to be downloaded and were corrupt. Ive since reverted to win7 and my s3...DNA wasnt cutting it for me but ill return to DNA later on down the road, what issue you having? getting adb? I had to change my usb drivers
nolimitzr2 said:
I did it, it was a pain however I had other issues with win8 such as all large file downloads would freeze up then my dl speed would skyrocket then appear to be downloaded and were corrupt. Ive since reverted to win7 and my s3...DNA wasnt cutting it for me but ill return to DNA later on down the road, what issue you having? getting adb? I had to change my usb drivers
Click to expand...
Click to collapse
Yes I am having trouble getting ADB. How did you change the USB Drivers?
art0605 said:
Yes I am having trouble getting ADB. How did you change the USB Drivers?
Click to expand...
Click to collapse
for me, to get the drivers to work i had to install htc sync.
If you plug in your phone, you should have 2 virtual cd's, one of them HTC sync.
After you get it installed, open a command prompt using administrator privileges (even though i am admin on my pc, i had to do this anyways)
and try running the command ADB devices and see if your phone shows up. that's what i had to do to get it to work.
Cdoan34 said:
for me, to get the drivers to work i had to install htc sync.
If you plug in your phone, you should have 2 virtual cd's, one of them HTC sync.
After you get it installed, open a command prompt using administrator privileges (even though i am admin on my pc, i had to do this anyways)
and try running the command ADB devices and see if your phone shows up. that's what i had to do to get it to work.
Click to expand...
Click to collapse
I am pretty sure I did the exploit correctly. But when trying to submit the token, I get Error Code: 160.
Try right clicking on the root program if there is an AIO and select compatability and chose windows 7
Sent from my SCH-I535 using Tapatalk 2
I rooted my phone a while back with a one click root process that rooted it to a rooted version of the stock rom. Recently I recieved notification that Jelly Bean is now available for my phone and that I need to connect to my computer via usb to update. But, my computer keeps getting a "device not recognized" error. I tried to install Kies for the drivers with no luck, uninstalled the drivers from Kies and installed the others straight from the Samsung website with no luck. I have tried 2 different computers and three different usb cables, including 2 oem usb cables. I have windows 7 which may be the problem. Are there any work arounds like going to stock from my sd card? My phone is no longer rooted, but for some reason still has Superuser which i can uninstall still. I brought my phone to Sprint which the guy was really cool and informed me that its not the usb port on the phone and that odin is recognizing it, but odin on my computers doesn't even see it.
Sent from my SPH-D710 using xda app-developers app
ultimate_reconx said:
I rooted my phone a while back with a one click root process that rooted it to a rooted version of the stock rom. Recently I recieved notification that Jelly Bean is now available for my phone and that I need to connect to my computer via usb to update. But, my computer keeps getting a "device not recognized" error. I tried to install Kies for the drivers with no luck, uninstalled the drivers from Kies and installed the others straight from the Samsung website with no luck. I have tried 2 different computers and three different usb cables, including 2 oem usb cables. I have windows 7 which may be the problem. Are there any work arounds like going to stock from my sd card? My phone is no longer rooted, but for some reason still has Superuser which i can uninstall still. I brought my phone to Sprint which the guy was really cool and informed me that its not the usb port on the phone and that odin is recognizing it, but odin on my computers doesn't even see it.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Did you have the Android drivers installed previously? I'm assuming that you're trying to install the drivers for the first time on that your computer and that you have USB Debugging enabled. I'll also be assuming you disabled driver verification, which can be a problem in some computers.
First you need to boot your phone normally, and plug it into the computer. Press Win+R to open the "Run" dialog and run "devmgmt.msc," which is the Device Manager. Look up the "Unknown Device" that is your phone and double click it. Click on the Event tab and check the Hardware ID in the drop-down box. It should look something like this (sorry mine is Android Composite ADB Interface because I've installed it already, but that's what it should look like in the end):
Now you have to make a new section in the driver inf. It should be in the google adt bundle and in the extras\google directory. The file name is android_winusb.inf. In the picture below my tablet is the iDeaUSA CT702. You need to add one of these sections in both the x86 and x64 section if you have a 64 bit computer. If not, just put it in the x86 section. The %USB stuff needs to match that in the Device Manager Hardware ID.
Now you should have a device called Android Composite ADB Interface or anything like that is fine.
It says there are no drivers and that there is no hardware id. All there is are device instance id. Im not quite sure where the driver.inf is located. This has been a pain for the past week. Hopefully we can figure this out. Lol.
Sent from my GT-N8013 using xda app-developers app
I think there may have been something wrong with the rom. If i could just reinstall stock i think it would work. Just need to get the USB to read to the computer.
Sent from my GT-N8013 using xda app-developers app
ultimate_reconx said:
It says there are no drivers and that there is no hardware id. All there is are device instance id. Im not quite sure where the driver.inf is located. This has been a pain for the past week. Hopefully we can figure this out. Lol.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
If you don't know where the driver is, then download a new one. I've uploaded the official Google USB driver to mediafire here: Mediafire - usb_driver.zip
You need to modify this driver, then when asked to select the inf file for driver installation choose the android_winusb.inf inside. After installation your phone should be recognized. Please tell me if there's any uncertainties you have.
Have you tried connecting the device with usb dev mode disabled? I know its strange but I've a few devices that use different drivers if the usb dev mode is enabled. I've also devices where I need to enable usb mass storage setting every time (settings menu or slide down notification). Also it never hurts to try a new cable, usb wires do tend to wear out and are very cheaply manufactured so they break inside with the slightest tug of the wire. I know most of this stuff is uber basic but I've made things much worse on countless occasions by overlooking simple stuff like this.
ultimate_reconx said:
I think there may have been something wrong with the rom. If i could just reinstall stock i think it would work. Just need to get the USB to read to the computer.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
Cha1n5aW said:
I know most of this stuff is uber basic but I've made things much worse on countless occasions by overlooking simple stuff like this.
Click to expand...
Click to collapse
Good point. If you don't have developer mode usb debugging enabled, then there will be no "unknown device" as shown above in the device manager. Be more detailed about "no luck" please.