Related
I just got my SNS yesterday and it's my first android phone (was previously using an LG cookie) First thing I did was try to root it, and I seemingly succeeded, or so I thought. It looks like it's rooted and the superuser apps there but I can't install apps using any of the guides I find or even update to 2.3.2 (keep getting and error 7 msg). When I try to install using APKInstaller it tells me it can't find the device, which I think is the problem.
I think the problem is that someway or another windows 7 64 bit stopped recognizing my phone as a Nexus S and now recognizes it as a portable device in device manager (There's also an Android Phone, with an Android Composite ADB interface) I used the SDK to install all the updates available including the google usb driver rev. 4. I tried updating the Portable device driver using the google usb driver but windows keeps it as a WPD Filesystem Volume Driver. Also I noticed when I checked to see if adb gave me a serial number for the phone using the cmd prompt commands in the rooting guides it comes up blank.
I used usbdeview to delete everything seemingly related to Android, but everytime I reconnect the phone it, installs the drivers for the portable device.
I need help to make windows recognize the phone as a nexus s again so I can update and install apps and games etc. If anybody out there can help i'll really appreciate it. Explain the steps to me as if you were talking to a child, leaving nothing out plz. Thanks for any assistance.
I live outside the US (no android market) and would hate to think I messed up and expense phone purchase in just one day
Not quite sure where to start. But my intuition tells me its the Windows 7 64-bit and drivers that's not playing along. You might want to google if other users are having trouble with W7 64-bit with Android drivers. Otherwise, find another computer and repeat the steps. If not, flash a custom ROM to see if that eliminates the problem. You haven't damaged your phone. Don't worry.
just install directly from android market website
Sent from my Nexus S using XDA App
I assume you mean instal the update from the market (which I can't do because I don't have wifi)?
I managed to get the adb to list a device number after I installed java x32 & x64 bit. I still can't install apps or get the update to work, but I'll try unrooting and then rerooting my phone as see how that goes.
Oh, I haven't done the initial sign into gmail thing yet in case that makes any difference
Edit: god I feel stupid. I didn't realize that I had to upgrade from 2.3 to 2.3.1 and then to 2.3.2. I did that an everything upgrade without any problems. Now just got to figure out how to install apk's and I'm golden
Edit 2: Ok, I figured everything out and now i'm up to date with updates and I can install apps and games. Oh Happy Day Thx for all the help
For those of you who have had trouble with getting the drivers for the Infuse, download this:
[Im new so cant post a link, but goto softpedia.com and search kies. The only kies program available will appear, and download and install that]
It wont recognize your phone, but after you install the program, the appropriate drivers will be present, and the root with SuperOneClick will work immediately.
*remember, the program wont recognize your phone if its plugged in, but that doesn't matter. It will just install the appropriate Samsung_Android drivers your PC needs to recognize the phone in SuperOneClick.
Hope this helps!
Hi , thanks , but ..
why not > http://j.mp/lOx2CB directly from samsung ?
pvillasuso said:
Hi , thanks , but ..
why not > http://j.mp/lOx2CB directly from samsung ?
Click to expand...
Click to collapse
404 Page Not Found
The page you requested was not found.
http://forum.xda-developers.com/showpost.php?p=13895587&postcount=7
posted here.
Phone doesn't exist on my PC.
Nope. Bought the infuse on day one. Installed Kies 2.0.0.11044_11_3. Phone not recognized, installed drivers, learned the truth about Kies. Phone would not be recognized but at least installing Kies made the phone visible to the PC, so I knew I could root if I so desired, read up about rooting and thought I was ready. The phone had other plans.
Decided the other day that I was ready to root. Plugged in the phone but it no longer showed up in Windows. Something about the phones compatibility with my system changed. Tried to install this Kies 2.2.1.11053_99_3 yesterday, reinstalled drivers, activated USB debugging, plugged the phone in started up SuperOneClick and . . . still nothing happened. So I deactivated USB debugging and started over. Followed all the directions in the root posts and and SuperOneClick threads . . .
But somehow between day one and today my Windows 7 64 bit system does not know that the phone is plugged into it.
When I plug the phone into USB the phone asks me how I want to interact with the computer, Kies (Firmware Update); Media player: Mass storage. But the computer shows nothing. Device Manager doesn't list the phone, Windows Explorer doesn't show the phone, Devices and Printers window shows everything that's connected but NOT the phone, it's as if I plugged nothing into the computer. The phone is charging so I know that it's plugged in, but it doesn't seem to be communicating with the PC. I've re-booted, re-installed, reviewed, rewired and re-alized that I have no clue what happened. (Tried different cables, different USB ports different times of the day)
It worked once upon a time, I tried rolling back restore points and disabling my kaspersky 2011, I've followed all rooting instructions in these threads to no avail.
I am now ready to hurl my phone out into traffic to see if that will help, but before I do I'm hoping someone here may have the answer I need.
. . . please . . .
Try removing all instances of the Infuse coming in contact with your system using USBDeView. Also, how does it look in Disk Management? (Start button > search for "Computer Management" > Storage > Disk Management) Does the Infuse show up there as removable storage?
For me, one of the SuperOneClick packages included Windows drivers.
Which is great since SOC is the only reason I needed Windows drivers. (SOC never works in Linux for me for whatever reason...)
All android phones are supported in linux natively.......jus t saying
Nopcodex90 said:
All android phones are supported in linux natively.......jus t saying
Click to expand...
Click to collapse
Well yeah - I've never had to install any drivers for ADB or anything else.
However, for whatever reason, superoneclick and Linux don't get along for me. So the only time I ever have to install drivers is when SOC rooting from Windows.
superweapons said:
Try removing all instances of the Infuse coming in contact with your system using USBDeView. Also, how does it look in Disk Management? (Start button > search for "Computer Management" > Storage > Disk Management) Does the Infuse show up there as removable storage?
Click to expand...
Click to collapse
Tried it, didn't work, oh wait, didn't run USBDeView as administrator, re-tried and uninstalled all instances of Samsung i-997, then tried to plug the phone back in and still nothing.
Also not in Computer Management or Device manager either. Is there a way to uninstall any drivers that I have and then re-install them?
M.
menzoom said:
Tried it, didn't work, oh wait, didn't run USBDeView as administrator, re-tried and uninstalled all instances of Samsung i-997, then tried to plug the phone back in and still nothing.
Also not in Computer Management or Device manager either. Is there a way to uninstall any drivers that I have and then re-install them?
M.
Click to expand...
Click to collapse
I've tried just about everything too, and nothing works to get my 64 bit Windows 7 PC to recognize the Infuse. Finally resorted to AndroidSync for file transfers, which worked fine, but it just makes me angry that I can't make the darn thing connect via USB.
http://www.samsung.com/us/support/downloads/SGH-I997ZKAATT
And select SOFTWARE
Tried that last week. Didn't work for me. The PC does see the device, but never finds any files on it.
Drivers in that link
I was having the same issue mentioned yesterday after loading the Samsung Infuse drivers, where my PC still couldn't see the data on my phone. (I'm also running 64-bit Windows 7 OS.)
Once I loaded the drivers and plugged in my phone, I got the happy little "device drivers installed properly" message and thought I was good to go. Nope. No drives mounted and visible in Explorer.
Under Devices and Printers, I could see SAMSUNG_Android with the unhappy yellow exclamation point. The troubleshooting report just says "Problems with PnP devices."
So I dug into into Device Manager. Under Portable Devices, there were 2 new WPD FileSystem Volume Drivers. Both had the same yellow exclamation points and showed a Device Status of "This device cannot start. (Code 10)."
It turns out Windows 7 wasn't assigning drive letters to the new Android volumes. It creates two disk drives (one with pictures, videos, and ringtones and the other with music, external SD, and media). If you right-click on the drives and choose "Change Drive Letter and Paths," click Add, and assign it an unused drive mapping, it will then appear in Explorer.
Incidentally, the SAMSUNG_Android still shows up with its unhappy yellow exclamation point in Devices and Printers. So I imagine there's supposed to be a more user-friendly way that doesn't expose the true internal file structure when it's all working properly. But in the meantime, I can at least access my phone data via USB.
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
neon_skunk said:
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
Click to expand...
Click to collapse
Dude look at the date
neon_skunk said:
Are you sure your not trying to root GB with superoneclick? Superonclick only works with Froyo.
Click to expand...
Click to collapse
Hey there..
View attachment 876861
thanks
Nopcodex90 said:
All android phones are supported in linux natively.......jus t saying
Click to expand...
Click to collapse
Yep...
Ubuntu / Linux FTW!
Hmmm, native on Linux you say? Don't have to battle with windows composite USB hub bullcrap you say? I shall try this.
Sent from my SAMSUNG-SGH-I997 using xda premium
hello and pardon by the English because I am translating.
I have a HTC S and I wanted one 2 days ago I put a ROM nandroip and everything but I realized and I wipe the entire phone erasing all the ROM and everything I had.
the problem is I can not install a ROM on my phone now because every time I try from windows CMD when you start the installation makes me daemon not running, and sends me error: device not found.
I've tried with another tutorial that you have with the application all in one kit but also not let me access this sd every time I try to enter telling me insert disk into drive E: \.
I can do?
I think it may be by the drivers of PC but not sure I instadao have 5 or 6 drivers and nothing.
an administrator's name is called android MYHTC ADB and other android or something.
I am desperate thank you very much took 2 days doing everything.
thank you very much.
my windows is XP.
Ok, Sorry but im having difficult understanding everything you say, But i think i got the basics.
I would suggest you re download the drivers, Remove HTC Sync if you have it. Move all of your ADB files in to 1 folder so its easier to navigate to when using ADB.
Can you boot the phone into recovery ? I assume you have CWM as you say you installed a nandroid ? If so, Use ADB whilst in recovery, USB Debugging is always enabled when in recovery so you should have no issues finding your device from there.
If all goes well and you find the device, You can then PUSH and INSTALL files / roms from there
Keep us posted
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
ericdg said:
Firstly, thank you for this great forum! I've already found a lot of great info on here, and love my new phone. I was trying to get drivers on my PC to start rooting my phone, but now that I can't even do that, I'm unsure that I should even be trying to root at all. Most, if not all of the driver's links that I've found here are dead so I tried a few other methods: Plugging in the phone after selecting USB debugging. Windows searched for drivers automatically, but found none. Downloaded HTC Sync, but it doesn't recognize my phone. I'm confused because I was already able to transfer my mp3's to the SD card via usb, but otherwise it seems like my phone isn't recognized.
My HBoot is the 1.45.0013, so I take it that it can't easily be turned S-off, but I probably don't need that anyway for what I want. I simply want to be able to remove all of the bloatware, and have access to functions like CPU control. For just that, I think that rooting while S-on will be fine?
I know that this is an old phone, but I bought it because the specs are still quite good, and I was able to get it brand new on Amazon for a song...............I would hope that there are at least drivers still available for it. Thanks for any help in advance!
~E
Click to expand...
Click to collapse
ADBSetup will get you the drivers you are looking for:
http://dottech.org/21534/how-to-ins...ows-computer-for-use-with-your-android-phone/
Worked for any Android phone I tried.
Thanks, I'll give that a shot and see what happens!
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
ericdg said:
Okay, I installed the driver from ADB, but still can't get HTC Sync to work...........................from reading other threads, it sounds like that's a common issue, though. Is there any way to confirm that I have the drivers installed? Under "devices and printers" on my PC, it will recognize an android phone when the phone is set to disk drive or charge only, but not USB tethering. When I switch the phone to the tethering option, the phone's icon on the PC moves from devices to unspecified. Then when I hover over it, it says there's no drivers. Again, I'm in debugging mode and have already copied MP3's to the SD, but I'd just like to confirm whether or not I have the needed drivers before starting the root process.
Thanks,
~E
Click to expand...
Click to collapse
Easiest way to tell is open up a command prompt in the folder that adbsetup installed to (C:\ADB I think) and type:
Code:
adb devices
If all is well, then the device will be part of the listing.
Thanks Joel.............I think it worked.
The ADB command came back with:
List of devices attached
HT22_______7 device
That's not a number that I've ever seen associated with my phone, but I assume that's it.
Confirmed.................I was able to reboot the phone by ADB!
Excellent! This will also mean the fastboot commands needed to unlock your bootloader will work too.
.........one would think so, Joel, but I can't get fastboot to do anything. ADB recognizes the phone, and will reboot into bootlocker, but once there it'll do nothing. Windows pops up a message shortly after bootlocker opens that says something to the effect of "there was a problem with USB device not recognized". I tried the command "fastboot devices", but got nothing. I know that I'm darned close, and it's probably something simple, but just can't get it to work. Maybe I need additional drivers for fastboot, or need to move it to another directory?
Thanks,
~E
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
joel.maxuel said:
Interesting. Try this:
Go into fastboot mode on the device, with the USB cable plugged in. On the computer, open up device manager. What is read for Android Device? Is there a noted problem with the driver? Open the properties for that device, and select Update Driver. The search process should find something appropriate now (as ADB Setup saves the drivers in the system32 folder - I think).
If not, what kind of user did you run ADBsetup as? If it was one without admin privileges, try installing again as admin (this allows the drivers to be saved where you want them to be).
If there are still problems, unfortunately I cannot think of anything else.
Click to expand...
Click to collapse
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
ericdg said:
I'm almost sure that the problem lies with the drivers now, but just don't know how to fix it!?! In device manager the phone moves into different categories, depending on the connection type; Charge only, and disk drive both work fine, but the icon for tethering shows no drivers installed. After rebooting into bootlocker the phone automatically switches to tethering, so I assume that's needed for getting root. I can't install drivers when the phone's in tethering from device manager, with either auto or manual. It just won't take! I've tried re-installing HTC sync, removing and re-installing multiple driver files, and the phone's just not being recognized. The sync instructions say that it should be a connection option on the phone also, but I've only ever seen the three: charge, disk, and tether. As for user, I'm pretty sure that I did install ADB as admin...............not sure how to check for that now, but the drivers are not in system32 like you mentioned; they're in program files (x86). Maybe the location of the drivers is the only problem I'm having, but I don't know where I want them to be? I hate quitters, but soon I'll just be enjoying the stock ROM for the best of it, if these problems persist!
Thanks,
~E
Click to expand...
Click to collapse
Dont know where you got your HTC drivers, but you should try the ones in this post (step one - hopefully its still live - if not I can dropbox it for you):
http://forum.xda-developers.com/showthread.php?t=1801106
Sent from my LG-D520 using XDA Free mobile app
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
ericdg said:
You're awesome, Joel!
That is the thread that I've been using predominantly, but I found that link to the drivers dead. I sourced them elsewhere, but couldn't really say where exactly since I've tried so many now. If you could dropbox for me, I'd really appreciate it.
Click to expand...
Click to collapse
Uh-oh. Either the link was dead when I went through this process back in April, or I had bad organizing skills at one point and didn't put the file in the Doubleshot folder before completing a purge. Either way, I don;t have the file.
Nor did I really need it. The second Doubleshot I rooted I ended up using it in my native Linux environment (no drivers needed), vs my Windows XP emulated through VirtualBox. That's what you could do. Get a live Debian DVD (Im like the XFCE desktop version), boot in, get fastboot:
Code:
sudo apt-get install fastboot
And then use fastboot:
Code:
sudo fastboot ...
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
ericdg said:
Thanks for the link and instructions; I'll probably not be able to try this for a couple of days now................just super busy, but I'll let you know how it went (or, more likely, have questions)! Any linux stuff is completely foreign to me, but it looks fairly straightforward. One question about the link that you provided, though: It looks like an index of a lot of individual files that I'd need. Under the parent directory, the folder named "iso-hybrid/ " is what I want, correct? I do really appreciate your time and help, Joel.....with as many dead links and outdated drivers that I've found, I don't think I could've got root otherwise!
~E
Click to expand...
Click to collapse
Just need the one. My recommended file to download is this:
http://cdimage.debian.org/debian-cd...ybrid/debian-live-7.6.0-i386-xfce-desktop.iso
Burn the image (not the file) onto a DVD (can be a rewritable) and reboot with the disc in the drive. Once it's fully loaded, you can either enter commands by clicking on the "terminal" icon on the bottom of the screen (preferred), or press Ctrl + Alt + F1 to get a prompt (may have to log in as "user", there shouldn't be a password). Hope this helps.
Hi all, first off im not a complete noob, I've rooted/bootloader unlocked a few phones, jailbroken apple devices etc... but this issue has me pulling my hair out now. Apologies if im in the wrong section of the forum.
So, i'm trying to unlock my bootloader on the OnePlus One using ADB through the Android SDK and i'm having several issues.
1 i cant get my phone to be recognised as an ADB device, have installed every single driver i can find anywhere, and none of it works, my phone has the necessary Developer Options enabled.
2 the Android SDK doesn't actually open for longer than a fraction of a second, i have tried multiple Java SDK's to direct the Android.bat file at, nothings happening for me.
3 i installed Eclipse to open the SDK in, Eclipse doesn't even open, it freezes
Im using Windows 10 on a HP630 laptop. Been trawling through the XDA forums among other forums and websites and im yet to find a solution, im about to try installing JDK 1.7 xxxx to see if i can redirect Android.bat to that version of the Java.exe
I'm aware of the process i have to go through to unlock my bootloader, its just i cant actually get the Android SDK to open, my phone to be picked up as an ADB device, and using Windows button +R to open ADB interface does absolutely nothing either, it flashes on for a fraction of a second and its gone again.
I'd appreciate any help anyone can offer me, im tempted to throw my laptop through the window.
JohnCSElwell said:
Hi all, first off im not a complete noob, I've rooted/bootloader unlocked a few phones, jailbroken apple devices etc... but this issue has me pulling my hair out now. Apologies if im in the wrong section of the forum.
So, i'm trying to unlock my bootloader on the OnePlus One using ADB through the Android SDK and i'm having several issues.
1 i cant get my phone to be recognised as an ADB device, have installed every single driver i can find anywhere, and none of it works, my phone has the necessary Developer Options enabled.
2 the Android SDK doesn't actually open for longer than a fraction of a second, i have tried multiple Java SDK's to direct the Android.bat file at, nothings happening for me.
3 i installed Eclipse to open the SDK in, Eclipse doesn't even open, it freezes
Im using Windows 10 on a HP630 laptop. Been trawling through the XDA forums among other forums and websites and im yet to find a solution, im about to try installing JDK 1.7 xxxx to see if i can redirect Android.bat to that version of the Java.exe
I'm aware of the process i have to go through to unlock my bootloader, its just i cant actually get the Android SDK to open, my phone to be picked up as an ADB device, and using Windows button +R to open ADB interface does absolutely nothing either, it flashes on for a fraction of a second and its gone again.
I'd appreciate any help anyone can offer me, im tempted to throw my laptop through the window.
Click to expand...
Click to collapse
Uninstall all other drivers and android sdk.
https://forum.xda-developers.com/showthread.php?t=2788632
Use this guide and all will be fine.