Related
Hello All.
I've had my UK, T-Mobile G1 for quite a while now. I have rooted it and it is running the latest CyanogenMod recovery image and ROM. I also have Apps2SD set up on my 8GB SD card, on a 512MB ext partition. This was all working fine until the problems below occurred...
I'm having some problems with several apps and ADB.
My PC runs Windows 7, 64 bit, and I can't seem to find a driver for the G1's ADB. I'm probably being incredibly stupid, but I just can't find one. I have used one before on Vista, where I had to set some boot options, but I'm not too sure / happy about doing that on my nicely functioning Windows 7. And as my friend once said; "You mess around with windows, then windows will mess around with you"...
But, anyway, I can't seem to get ADB working, if someone could either send me a link to the drivers or guide me through it, I'd be grateful...
Also, it may be due to me running CyanogenMod, but if I try to update the Facebook app, it downloads the app, and then when it tries to install, gives me the error "Installation Unsuccessful - Incompatible Update".
And with the Google Maps app, it says "Installation unsuccessful - Package file was not signed correctly". This may be due to me trying to get the hacked version of the app to get the Google Maps Navigation working in the UK, but I couldn't get that to work, so I uninstalled it and Nav Launcher, and now when I try to update from the Market it gives me that error.
I've seen a guide online with ADB commands, but as I have no access to ADB, I'm a tad screwed. I've tried runnign the commands in the Terminal Emulator in the phone, which does approximately nothing whatsoever.
So, can anyone give me any guidance on any of my Android problems?
Thanks in advance - Ethan
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
jamesrdorn said:
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
Click to expand...
Click to collapse
Ah. Looks like I'll be reinstalling Ubuntu then for the ADB. Thank you for such a fast response.
- Ethan
jamesrdorn said:
To the best of my knowledge no one has successfully used ADB with Windows 7/64bit
Click to expand...
Click to collapse
Lies, I'm running windows 7 64bit and ADB works fine.
chris4500uk said:
Lies, I'm running windows 7 64bit and ADB works fine.
Click to expand...
Click to collapse
In that case, do you remember where you obtained the driver from? I would love a link, or a zip file or something...
I'm on Vista x64 SP2 and I can use ADB just fine. You just need to download the SDK and then get the USB driver through there. It used to come included, but now you need to use the ADV and SDK manager and download the drivers as an SDK Component through there.
After that, make sure your phone is set to USB Debugging mode and plug it in then point windows to the new drivers. If it doesn't want to install the new drivers, you might need to remove the old ones first. I had to use USB Deview (DL link at bottom of page) and removed all installed HTC drivers. After that I plugged my G1 back in, pointed it at the newly downloaded drivers and all was well.
I'm running adb/fastboot/android sdk on win7 64b ultimate. The drivers are included in the sdk download. Once you download the sdk, make sure you have java installed. (I had to install JRE and JDK to get it to work properly, not sure if this was needed) Anyhow, when you have the sdk downloaded, run the sdk setup program. Go to settings and check the box for force update (unsure of the exact terminology used there) then go to available updates and your drivers are the last option on the list.
It's probably just because I HAVENT USED IT IN AGES...but I have the USB driver package installed in my sdk and I guess I forget where to go from there. It works fine on my XP...I believe I'm missing the Nexus one drivers that usually install automatically but they aren't...am I?
Please and thank you for the help. I hate change :]
couldnt get adb to work on my win7 either, for some reason qtadb works perfectly, so if that suits your needs i would just use that.
Hm Ok it just keeps saying connect your phone. Could it be because I'm missing the nexus one drivers? Because they wouldn't install when I plugged my N1 in.
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
Thanks to vbrtrmn's post about his problem on the Q&A forum, I realized I lost the use of SU with todays update. I don't know why (maybe someone else can shed light on this or if this), but it did more than just that, it also broke ADB!
I don't know much about ADB so I am approaching this with limited knowledge, but I hope it helps. I do not take responsibility for any problems you may have!
Also please note that these are not instructions on getting adb and su working from scratch (although they could easily be adapted to do so)
OK! So after some messing around, I was able to get ADB and, in turn, SU working again.
First thing you'll have to do is plug the OUYA into your computer via USB and delete all the OUYA drivers from your Device manager. From what I could tell, the OUYA stopped showing up as an Android Phone ADB Composite device (hence the ADB problem). After you delete the drivers, unplug the OUYA and then follow steps 5-12 (windows) on this website: https://devs.ouya.tv/developers/docs/setup .
Once you get to step 13, you don't actually have to hit the Have Disk button, just select ADB Composite Device from that screen (it appeared for me, may not for you, you might have to follow their directions). This will take you to step 14 and 15 on that webpage.
After that is done, then head over to the original instructions on this forum, found at: http://forum.xda-developers.com/showthread.php?t=2272266
The only thing you should have to do is step 4 under HOW TO INSTALL BUSYBOX, SUPERUSER, AND SU BINARIES, assuming you already have the files in place.
This SHOULD give you access to SU and any apps that require it once again. To check, go to Make on your OUYA and open the Superuser app. If it asks for root permission, it worked.
The only problem I ran into is that the OUYA is now only recognized as a adb device and has a broken MTP driver (whatever that is, maybe someone else will know) on my computer. Maybe this is how it's supposed to be, I don't know, I don't remember seeing anything like that the first time.
Again, I know very little about the drivers, adb, and/or su so if I got anything wrong, please let me know!
EDIT: Make sure to try hard resetting the OUYA before trying this. While it didn't work for me, that's what fixed vbrtrmn, but he was not on Windows.
JLCollier2005 said:
EDIT: Make sure to try hard resetting the OUYA before trying this. While it didn't work for me, that's what fixed vbrtrmn, but he was not on Windows.
Click to expand...
Click to collapse
I was using a Mac .. Hard boot both the OUYA and Mac, seemed to fix my issue. Not sure why exactly, killing adb should have done it, oh well.
The OTA update did wipe out my settings in build.prop for wireless adb.
Hello,
1. Downloaded kalilinux.FULL.ext4.20131031.zip of around 2.2 GB.
2. Extracted zip on sdcard in kali folder and I got kalilinux.FULL.ext4.v2.img of 5.59 GB.
3. Installed Linux deploy from play store.
4. In the Linux deploy tap on right bottom download button and selected Kali Linux as distribution option, installation path /sdcard/storage/0/kali/Kali.img (I renamed the img).
5. Clicked on install option from menu option. Did not worked, got message something like Mounting Partitions... fail.
6. OK. I left this way and installed Linux deploy and reinstalled Linux deploy and installed kali Linux from Wi-Fi connection, it seems it got worked and after seeing many retrieving, validating, installing and configurating messages in Linux deploy, it seems me got installed.
7. But, I don't know how do I access Kali Linux on my this one plus one device which is running aicp 7.1.1 ROM.
Kindly tell me what step(s) need to run Kali Linux on my phone. I am interested to use above Kali.IMG, so that a fresh new installation can use this IMG which have bundelled many pre configured modules.
Do you have a VNC client?
SirSoviet said:
Do you have a VNC client?
Click to expand...
Click to collapse
Thanks for your reply. Yes sir, I have installed vnc app too, but I don't know what settings I need to have. I tried by localhost and Kali for connect, but it is saying "The port on which computer is listening for a connection could not be contacted". I don't know which "computer" is it talking about and what port I need to use?
GirishSharma said:
Thanks for your reply. Yes sir, I have installed vnc app too, but I don't know what settings I need to have. I tried by localhost and Kali for connect, but it is saying "The port on which computer is listening for a connection could not be contacted". I don't know which "computer" is it talking about and what port I need to use?
Click to expand...
Click to collapse
Sorry, I can't get it working on my device either :/ I just need to figure it out, I'm 100% sure it would work with the correct settings...
SirSoviet said:
Sorry, I can't get it working on my device either :/ I just need to figure it out, I'm 100% sure it would work with the correct settings...
Click to expand...
Click to collapse
Ok, no problem. Please share with us as and when you get success by installation and running Kali on the phone. I would like to request to other xda experts to please tell us how they are able to install Kali with offline .IMG file and other vnc settings.
May I ask here?
After installation kali runs as a normal operating system, not as an app, correct?
Does it run as a dual boot OS?
r0tati0n said:
May I ask here?
After installation kali runs as a normal operating system, not as an app, correct?
Does it run as a dual boot OS?
Click to expand...
Click to collapse
Well, it does run as a normal operating system, but it's sandboxed into an app. It's like a virtual machine.
i love Kali on my OnePlus One.
i use it with a micro USB to LAN Adapter for do anything what i will do with Kali
GirishSharma said:
Hello,
1. Downloaded kalilinux.FULL.ext4.20131031.zip of around 2.2 GB.
2. Extracted zip on sdcard in kali folder and I got kalilinux.FULL.ext4.v2.img of 5.59 GB.
3. Installed Linux deploy from play store.
4. In the Linux deploy tap on right bottom download button and selected Kali Linux as distribution option, installation path /sdcard/storage/0/kali/Kali.img (I renamed the img).
5. Clicked on install option from menu option. Did not worked, got message something like Mounting Partitions... fail.
6. OK. I left this way and installed Linux deploy and reinstalled Linux deploy and installed kali Linux from Wi-Fi connection, it seems it got worked and after seeing many retrieving, validating, installing and configurating messages in Linux deploy, it seems me got installed.
7. But, I don't know how do I access Kali Linux on my this one plus one device which is running aicp 7.1.1 ROM.
Kindly tell me what step(s) need to run Kali Linux on my phone. I am interested to use above Kali.IMG, so that a fresh new installation can use this IMG which have bundelled many pre configured modules.
Click to expand...
Click to collapse
May I ask you why did you install it as a guest os and not as dual boot with Multirom?
SirSoviet said:
Sorry, I can't get it working on my device either :/ I just need to figure it out, I'm 100% sure it would work with the correct settings...
Click to expand...
Click to collapse
Hi again,
Have you worked on it please? I don't know how people are using Kali Linux on phone?
GirishSharma said:
Hi again,
Have you worked on it please? I don't know how people are using Kali Linux on phone?
Click to expand...
Click to collapse
I tried it a couple weeks ago and it's surprisingly functional. Here's my settings: https://drive.google.com/folderview?id=0B1HrmNJiLNhjb04ydWlpaktPNkU
Press the button at the bottom-right, configure, then go back, press the three dots at the top then press install. After it's done, go to your VNC app of choice (I use VNC Viewer), add IP address localhost:5900, connect then enter user password. Ta da!
Btw, the reason you couldn't get it working is because you downloaded an image and used that, when Linux Deploy does everything for you.
SirSoviet said:
I tried it a couple weeks ago and it's surprisingly functional. Here's my settings: https://drive.google.com/folderview?id=0B1HrmNJiLNhjb04ydWlpaktPNkU
Press the button at the bottom-right, configure, then go back, press the three dots at the top then press install. After it's done, go to your VNC app of choice (I use VNC Viewer), add IP address localhost:5900, connect then enter user password. Ta da!
Btw, the reason you couldn't get it working is because you downloaded an image and used that, when Linux Deploy does everything for you.
Click to expand...
Click to collapse
Thanks for your reply. I will try your way when I will be in WiFi network area. Since, in my region network issue exists, I want to learn Kali installation by offline downloaded zip file so that :
1. Network issue can be override.
2. If I changes the ROM, I can play with zip on different ROMs.
So, please give a try by installing zip file as and when you gets spare time and kindly post your offline steps.