Related
To this point I have managed to root and unlock my Captivate with great success. I have also managed to run various ROM's, Cognition, Serendipity, Paragon, etc.
I was using Serendipity 5.3 and the Steam kernel, I tried adding afterburner features and have now gotten stuck. The phone continues to reboot into steam recovery and I can navigate, but always receive "Partition /res/.fake/gingerbread/system could not be mounted! What should I do?"
I can get into download mode very easily by pulling the battery, putting battery back in, holding vol up and down then plugging phone into usb cable. From that point it just hangs plugged in or not, no communication with the pc, I can see the device as an Android UMS composite drive but can't write to the drive. I have tinkered in the console mode from Steam recovery and some of the usual commands will work such df -h to see drives and size, ls shows all the contents on the phone.
I run Linux on both my desktop and laptop, I have Xp in a VM with USB support, it shows as a Nexus device but Odin will not communicate with the device either. I have tried Heimdall, but receive the following.
Claiming interface... Success
Setting up interface... Failed!
I originally used Heimdall when flashing the first time then moved to CWM and never had an issue until I began fooling around with the kernel.
I'm hoping this is a repairable situation, maybe using the console in steam recovery? Just not sure what the commands might be or I may be barking up the wrong tree altogether.
Thanks in advance for any help offered.
Hi all,
I am noticing something with nexus s.
When in recovery or in normal homescreen, my nexus s communicates properly with adb commands
But there seems to be no communication from the nexus s when in fastboot mode.
Everytime I enter a fastboot command, I always get a "waiting for device" and nothing happens.
Am I missing something?
Thanks.
Heeter
If your PC is running Linux then you will need to be root.
No I am running windows 7
I got the Android 1.0 driver. Windows Device manager recognizes that my phone is hooked up,
But when I type in "fastboot devices" it is not listed there.
Thanks
Heeter
When I hook up my Nexus S in fastboot mode, I see this at the bottom:
Code:
USB Control Init
USB Control Init End
STANDARD_SET_CONFIGURATION
Everytime I unplug/replug USB wire, another "STANDARD_SET_CONFIGURATION" line gets added
I type "fastboot devices" into fastboot, and my Nexus S does not show up.
The phone is currently unlocked, but I would like to lock to reset it and start from factory rogers setup again.
Any help would be greatly appreciated.
Thanks
Heeter
You need to install "PDAnet"...search pdanet on yahoo and you will find the website to download it....it has the right drivers for your computer to communicate with your phone.
download it...and before you install it...make sure your phone is connected to your computer and in fastboot mode.
after install your phone will work in fastboot mode..you do not need to install pdanet on your phone
::thanks??::
rubbamade said:
You need to install "PDAnet"...search pdanet on yahoo and you will find the website to download it....it has the right drivers for your computer to communicate with your phone.
download it...and before you install it...make sure your phone is connected to your computer and in fastboot mode.
after install your phone will work in fastboot mode..you do not need to install pdanet on your phone
::thanks??::
Click to expand...
Click to collapse
I do have that already, rubbamade.
My Device Mangler is recognizing Android 1.0, and has the drivers for that I took from PDAnet.
The PDAnet itself couldn't install properly, so I extracted the drivers from the package and manually installed them through the Device Mangler.
I still cannot connect to fastboot.
Heeter
I am moving back to Debian,
Had enough of Windows.
Only moved to it because I bought Crysis2 on Steam.
Never had a problem with SDK, ADB and fastboot, until I was on Windows.
Thanks again,
Heeter
I guess you made your decision already in getting rid of windows lol. Anyway goodluck with the fastboot issue. And I hope the 3G issue is looooooog gone from your life. Take it easy
Arnel
Sent from my Nexus S using Tapatalk
LOLOL,
A whole bunch of thanks for that radio to you again
Heeter
Good choice ditching windows. Lol
Offtopic: how is debian compared to Ubuntu concerning repo n 3rd party drivers? Seriously considering switching to debian since Ubuntu adopted the crapy Unity
Sent from my Nexus S using Tapatalk
The driver isnt right if your phone wont show. You have to let windows find the correct driver out of the drivers you point it to. Either point it to x64 or x86 directory only. No further. Windows will find it.
Go to the fastboot thread in development and get the drivers.
Uncle Jimmy says hello
Heeter, it's maybe a bit late but unless you're really strapped for disk space you can keep Windows and create a separate partition for Linux, using the grub bootloader to choose between the two. I'm a Linux user myself (mostly Arch but I love to test most new distros) but I have lots of disk space and I keep an up-to-date Windows 7 installed for testing purposes and gaming.
Since - I have to admit it - I suck at most games, my Windows doesn't get used much but I don't begrudge the space it takes up. On Debian you should have less trouble with the adk and drivers - here's a good post at Howtoforge about using the adk http://www.howtoforge.com/setting-up-an-android-app-build-environment-with-eclipse-android-sdk-phonegap-debian-squeeze
Heeter said:
I am moving back to Debian,
Had enough of Windows.
Only moved to it because I bought Crysis2 on Steam.
Never had a problem with SDK, ADB and fastboot, until I was on Windows.
Thanks again,
Heeter
Click to expand...
Click to collapse
First, just uninstall your Android 1.0 device driver completely and...
All you need to do is connect to USB at the standard Android homescreen (with debugging on), then in command prompt, make sure it loads properly in ADB when fully booted...
"adb reboot bootloader" and let PDANet work its magic, it will pull your drivers and install for you. If you disconnect, it will not pull the right driver.
bender_123 said:
First, just uninstall your Android 1.0 device driver completely and...
All you need to do is connect to USB at the standard Android homescreen (with debugging on), then in command prompt, make sure it loads properly in ADB when fully booted...
"adb reboot bootloader" and let PDANet work its magic, it will pull your drivers and install for you. If you disconnect, it will not pull the right driver.
Click to expand...
Click to collapse
I tried that like 50 flippin times! everytime, PDAnet stays locked up during the pulling driver area. I have come back half hour later, still not complete. Then, when I unplug the cable, it spits out an error, and uninstalls itself.
What I ended up doing was, during the PDAnet install, it creats a root folder in C:/Program Files/PDAnet (or whatever it is). Now when it got stuck there, I went into that root folder, copied the "usb-win" driver package from there and set it aside. Then I went into the Device Mangler, and right clicked and manually installed the PDAnet driver.
Hiya Gun26, Thanks for that link. I am actually a site supporter on that site, if you search up "Heeter" over there. Been for a couple of years now.
I guess I could go back to dual booting, haven't done that in a long while either.
Heeter
That was just a suggestion about the dual booting - if you enjoy gaming, why give it up? Linux and Mac may be great (and BSD let's not forget) but for gaming it's either Windows or a console. I don't think you'll have any trouble with the adk and drivers on Debian. Good to hear about your connection to Howto Forge - it's a really useful site.
Thanks for that Gun,
I haven't had time to move back to Debian, and I really do like gaming once in a while.
I should be up and running dual boot this weekend.
Thanks again, guys.
Heeter
i'm having this same problem, it's rather annoying
UPDATE-SOLVED: So I used the terminal command dmesg to see what errors were coming up relating to the usb port. It turns out I was getting the popular "unable to enumerate usb device on port..." error. From a google search on this I was able to find other people with my same problem, albeit with other types of devices not working on the usb ports. So someone tried a simple fix and worked. Ill quote it here just for the sake of keeping you on this page...
Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:
Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2
After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.
Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:
1: cd /sys/bus/pci/drivers/ehci_hcd
2: ls
You will see a file with 0000:00:xx.x format. Execute the following command:
1: sudo sh -c 'echo -n "0000:00:xx.x" > unbind'
#Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.
I plugged in my memory stick, and it worked.
Please note that you’ll have to do all this each time you restart.
UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:
1: cd /sys/bus/pci/drivers/ehci_hcd/
2: sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'
Cheers!
Ok so I just finished installing a fresh copy of Ubuntu 11.04 on my g/f's old Sony Vaio from 2003/04. I tried plugging in the Infuse to see if the computer will recognize it. So when I select 'Mass storage' from the connection menu, the connect screen with the green android robot will pop up for a split second, then disappear. So there is no way for me to mount the phone to the computer. The option doesnt even appear in the notification bar. Sometimes the robot screen wont even appear at all. I check the cable, and it works 100% fine on my win 7 64 bit pc. It just doesnt seem to want to do anything on the Ubuntu pc. The phone will charge, but thats about it. Im running the clean Gingerbread update on the Infuse. Nothing modded, and as i said, the Ubuntu is clean install as well. Ive tried this with usb debugging on and off. Ive also tried restarting both phone and pc and nothing changes.
Any help would be so greatly appreciated. Thanks a million.
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Dani897 said:
weird. try other USB devices. you could have motherboard driver issues.
I'd check the Ubuntu forums and see if others with that hardware have any issues with USB devices. you may need to find some alternative drivers that aren't in the stock Ubuntu build or find a different computer.
Click to expand...
Click to collapse
I have tried some flash drives. They seem to work just fine. When I plug the phone in under the mass storage option, I open up a terminal and type usb-devices, and i see the three ports listed, but it shows that nothing is being detected on any of them.
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
dubuntu said:
Linux driver should be perfect, before connects to PC the mass storage mode should be selected.
Click to expand...
Click to collapse
I made sure it was selected. I also just got finished setting up the Android SDK on the Ubuntu laptop. ADB does not recognize that the device is plugged in at all. It can see my flash drives, but nothing comes up for my phone. Even with usb debugging on it did not see it. Im at a loss. Im beginning to think that this may have something to do with the Gingerbread update. Can someone with the update try to connect to Ubuntu and let me know if they have success? Ide hate to have to revert my device to Froyo or an unofficial rom to develop. =/
well I see you fixed it. did you get adb going?
Dani897 said:
well I see you fixed it. did you get adb going?
Click to expand...
Click to collapse
Yes! How?
Sent from my SAMSUNG-SGH-I997 using Tapatalk
are you asking how he fixed it?(he updated the op if that's what you are interested in) or how to get adb going.? adb works on Ubuntu as long as the device connects but you need to setup some device information first.
I forget the location but you need to create a file called 70rules.android (if my memory serves me right) with the vendor I.d and some other information. let me know and ill find a link on it.
Yes! I was able to finally get adb going after I had fixed the USB detection. Once I had applied the changes above my computer would immediately recognize the phone in both normal and debug mode and I could transfer files to and from it freely. Also, typing in ./adb devices finally showed my device as being connected with the proper vendor id as well.
The file I believe yyour referring to is named 70-android.rules and its only part of a whole process on getting the sdk setup on the laptop. There are a lot of hits for setting g it up on Google. There is also a whole guide for this here on xda which I had followed.
Sent from my Samsung Silly Phone
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
MissBizz said:
Alright, here goes my first post. I have lingered in these forums for awhile, and have always found what I needed. This is the first time my searching on here, as well as google, has let me down.
To clarify, if I connect to my computer and have USB Mass Storage on, I can see it, move files to it and everything. My problem is, I am using my old phone (P500) to learn and practice ADB (I own a GNEX), and would like to install CWM via ADB, but I need to move files to the root of my sd.. but my phone won't show up if it's in debugging mode!
I have the drivers installed, and used a toolkit to root (worked fine, no errors). Am I missing something here or is there another issue?
Info:
Windows 7 64bit
Telus Mobility (Canada)
Model: LG-P500h
Android 2.3.3 (stock)
stock kernel
Click to expand...
Click to collapse
Since the device is not getting detected with USB Debugging enabled it's safe to assume a bad driver installation. To verify tho, enable USB Debugging on the device and connect it to your PC. Go to Device Manager. Somewhere towards the top, assuming the drivers were installed will be a device "ADB Interface" with a subitem "Android Platform Sooner Single ADB Interface" or something similiar. If the "ADB Interface" item isn't there then the drivers weren't installed correctly. Uninstall them. Reboot computer. Rerun driver installation program. When it finished, reboot your PC. Power off the device. Connect it to your PC. Power on the device and let all drivers install. You should be good to go from here.
If you'd like a good known set of LGE USB drivers, download Android Flash Recovery, link is in my signature. Hope this helps.
EDIT:
Oh, and Welcome to XDA
I have an rca tablet I can not get any drivers to work to get to replace/update the firmware and I was wanting to ask if anyone has found anything that works.
I have tried mediatek, rca and all other drivers I can find and nothing seems to work on windows 10 64.
Thank You
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
xXx yYy said:
DL here:
Download Android USB drivers for RCA - HEXAMOB
Download Android USB drivers for RCA. Here you can find available USB Drivers for your Android phone and tablet. In this updated section, we try to help you find all types of downloads, links and help to connect your Android device to your PC.
hexamob.com
Click to expand...
Click to collapse
Thank You will give a try
I have a Windows 7 64 bit system and I am trying to find drivers to access an rca rct6703w13
I have tried every driver I can find and nothing seems to work does anyone know something that will work?
I would be very grateful if anyone could help?
Thank You
Oh boy, I still remember this pain trying to find and use such drivers on Windoze:
- try another port
- try another cable
- try this driver or that one
- try doing a rain dance with 3 days old undies on your head, and turn only clock wise, unless it's full moon, then turn counter clockwise but stop briefly after ever two and a half turns
Maybe, as workaround, you could boot from a linux CD and try your approach from there.
Whenever I flash from my debian, it works: If "fastboot devices" still doesn't show anything then usually I have forgotten to plugin the cable
By using my "Yet Another Universal ADB Driver" Package (see the link in my signature) one can remove all the old adb drivers if that is the issue, but this case seems to be more interesting...
On win10 it seems that the adb is embedded to the winusb driver the same or similar way (registry wise) that my package is using. Now that I have tested, the behavior is similar with my devices. When using file transfer connection the adb is not recognized. With others, charging, photo, midi the abd works fine. To make adb work with file transfer one have to install the correct driver. In this case google's general driver could be okay, one match for vendor and product ids in it ...
https://dl.google.com/android/repository/usb_driver_r13-windows.zip
What I tested using virtual win7 64bit, it seems to behave the same way... which is a bit weird as I've tested it with my driver package. Worked okay then I think. The Android device used has changed since though.. It worked on win10 back then too.. the change has to have happened later.. or I didn't use file transfer..
@steadfasterX 's maid or salt or whatever it's called nowadays might be usable in this case. It's a Linux having SP flash tool etc. available..
edit: tested and it turned out that the updated phone is the problem... using another phone my driver package worked as expected..
@resxwni01
1. Don't confuse USB-driver and ADB-driver: the USB-driver since ever is by default part of any OS, so also of Windows OS. The ADB-driver is an extra protocol what allows you to communicate with a phone's Android ecosystem via an USB-connection.
2. Latest generic ADB-driver ( correct: ADB client ) got released August 2022 and is officially versioned 33.0.3.
3. AFAIK a 64-bit version of ADB-driver doesn't exist.
With regards to install this ADB-driver on a Windows 7,8.1,10,11 PC:
It's NO USB-driver installer - as introduced above by @CXZa - needed what unnecessarily bloats the Windows registry with crap.
You
1. simply create on any mounted drive of Windows PC a folder named "ADB",
2. extract there to the 3 files what are in the attached ZIP file,
3. add path of created folder "ADB" to Windows environment variable PATH, thus ADB-driver is systemwide accessible -
how to is described here
How to Set the Path and Environment Variables in Windows
Information on how to set the path and environment variables in Windows 2000, Windows XP, Windows Vista, and Windows 7.
www.computerhope.com
@jwoegerbauer , you're funny guy...