I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
'USB Debugging' enabled?
Of course. It will install drivers for the ADB device, it just won't be detected by adb.exe.
I tried the 'switch to Photo MTP' mode trick too. I am having no issues with adb to a One XL, One V, Defy, Aurora II or U8800. This is really bizarre.
Do you have java jdk installed correctly?
http://www.oracle.com/technetwork/java/javase/downloads/index.html
I wasn't aware java was relevant to adb at all (and I don't think it is) but yeah I have the JDK installed and it works fine for my app dev.
I had the same issue. Drivers installed correctly (and worked on other phones) but not the N4.
In the end i used an Ubuntu Virtual machine, attached the phone, followed a guide on XDA for getting ADB drivers in linux, and it worked straight away.
Days of trying in windows, and done in 5 minutes through linux.
Yep, I too went the virtual machine route.
Ridiculous. The only two developer devices I've owned (Nexus S and Nexus 4) and they've both been impossible to get the adb drivers going...
Passa91 said:
I wasn't aware java was relevant to adb at all (and I don't think it is) but yeah I have the JDK installed and it works fine for my app dev.
Click to expand...
Click to collapse
Yes you have to have installed the java jdk to run adb, it doesn't work without it. Java jdk is supposed to be setup first before you install the sdk so that it finds it. One issue why people can't get adb working is that the path environment variables are not set up and need to be manually entered.
Example of setting your windows path environment variables for jdk version 6 windows 32 bit on Windows Vista.
right-click on My Computer, and select Properties
under the Advanced tab, hit the Environment Variables button
in the dialog that comes up, under System Variables double-click on Path
Add ;C:\Program Files (x86)\Java\jdk1.6.0_18\bin to the Path variable (or wherever the jdk was installed)
Add ;C:\android\android-sdk-windows\platform-tools to the Path variable (or wherever you installed the sdk)
Passa91 said:
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
Click to expand...
Click to collapse
I posted a solution some time a go find it in my posts
Sent from my Nexus 4 using xda premium
davehunt83 said:
I had the same issue. Drivers installed correctly (and worked on other phones) but not the N4.
In the end i used an Ubuntu Virtual machine, attached the phone, followed a guide on XDA for getting ADB drivers in linux, and it worked straight away.
Days of trying in windows, and done in 5 minutes through linux.
Click to expand...
Click to collapse
The linux guides include editing the udev rules so that you manually enter the Nexus 4 into the list of devices in order to get adb to recognize the phone. Could be the same issue with windows. I only have the sdk installed on a Linux box and haven't used it on windows since I installed it on a Vista box a few years ago but I would imagine windows would have the same problem recognizing the phone.
Linux Install Instructions
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Passa91 said:
I've tried every driver known to man. I've tried the official Google drivers, I've tried the naked drivers, I've tried the ones that come with PDANet.
I've tried rebooting, uninstalling all other drivers, etc. I tried on my Windows 7 desktop, I tried on my Windows 8 laptop after disabling driver enforcement.
Every single time, the ADB driver installs fine, but adb itself sees no devices. I develop, I have many other Android devices (I am moving from a One XL) and they all just need one quick install and are detected. I have the same issue with my Nexus S - getting it consistently recognised on ADB is near impossible.
What am I doing wrong? I've waited three months for this thing and I want to set it up.
Click to expand...
Click to collapse
I used the Universal_Naked_Driver_0.72. It worked for me. I did not install Java.
http://dl.dropbox.com/u/18573149/Universal_Naked_Driver_0.72.zip
RacerXO said:
I used the Universal_Naked_Driver_0.72. It worked for me. I did not install Java.
http://dl.dropbox.com/u/18573149/Universal_Naked_Driver_0.72.zip
Click to expand...
Click to collapse
You shouldn't even be able to install the sdk properly without having java jdk installed first as the windows installer checks to see if its there.
http://developer.android.com/sdk/installing/index.html
Edit: and by installer I meant SDK Manager, what you use to download and install the android usb drivers. I suppose you can get past the java limitation by just downloading the sdk and copying the needed files into the c directory then using 3rd party drivers but java jdk is what controls the phone once its connected so I don't know how you are getting it to work.
Edit 2: I guess I was wrong in part, I installed the sdk without java jdk on a windows xp box, used the universal drivers linked to above, and it recognized my phone in adb devices and I was able to reboot it. But I can't use sdk manager as it requires java jdk to be installed.
had the same issue... you must be using a usb port on the front/side of the computer
use one of the usb ports on the back, and you should be just fine.
This happens to me too. On all windows computers I have used for ADB and all phones it will work the first few times, and then it won't work no matter what. I can usually get fastboot to work reliably but that is it.
Sent from my Nexus 4 using Tapatalk 2
Related
Is anyone else having an issue with drivers running a 64 bit system, I cannot do anything from cmd line on my 64 bit desktop but from girls laptop i can root and use all the commands wtf
i have windows 7 32bit and mine is working good here is the driver i used for adb
BrianDigital said:
Is anyone else having an issue with drivers running a 64 bit system, I cannot do anything from cmd line on my 64 bit desktop but from girls laptop i can root and use all the commands wtf
Click to expand...
Click to collapse
It's probably your environment settings. Download the sdk and make sure your PATH has the extracted sdk folder location in it. I'm using windows 7 64-but ultimate, and did have a few problems at first, but everything is great now.
Also, I installed the Java Runtime Environment on my machine because I was developing an android app and I need it to run files within the SDK (like to make an emulated sdcard). You may want to install the JRE and add that to your PATH as well.
Google HTC sync x64 drivers. I installed a few weeks ago and had no issues with adb today.
oh sorry i thought thats what you meant
installed the HTC 64 bit drivers and still no go I cannot even use htc sync
I had a problem getting the device to work in cmd with xp64. I had to make sure I had a working ADB driver. One blog by a guy named Chris Bunney said to use PDAnet's driver. Basically install the 64 bit version of PDAnet in order to get the driver and then uninstall if you're not going to use it (but make sure you have the driver set up first). If you've already got a driver installed, go to the driver and manually pick "HTC Dream Composite ADB Interface" as the working driver for the device. Again, this is how I got it working on xp64 not sure how it'll go for windows 7 64 bit.
BrianDigital said:
installed the HTC 64 bit drivers and still no go I cannot even use htc sync
Click to expand...
Click to collapse
Did you use the updated driver from THIS link? Beyond that I have no other idea what to tell you beyond putting the android sdk in the root of your c: drive.
I just tried this on my girlfriends laptop with 7 x64 pro (completely fresh), and had no issues.
I had the same problem, this guide and some googling got me up and running quickly.
http://gadgets.softpedia.com/news/How-To-Solve-HTC-Hero-Sync-Problem-in-Windows-7-4442-01.html
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.
I've been trying to root this thing for about 3 hours now. I'm on Windows XP and I can't get my kindle to be recognized in adb. I've tried updating my drivers in SDK and still no dice. All the guides appear to be for windows 7. Nothing I do is working. I've rooted several devices including tablets in the past but this one is almost impossible. All I want is the android market on my kindle.
ddgarcia05 said:
I've been trying to root this thing for about 3 hours now. I'm on Windows XP and I can't get my kindle to be recognized in adb. I've tried updating my drivers in SDK and still no dice. All the guides appear to be for windows 7. Nothing I do is working. I've rooted several devices including tablets in the past but this one is almost impossible. All I want is the android market on my kindle.
Click to expand...
Click to collapse
Uhm... I'm not so sure about windows XP when it comes to automatically searching for drivers, but turning on the USB debugging setting might get windows to download everything necessary for adb to recognize the device. It worked on my phone, when I couldn't find the drivers... Just turned on USB debugging under "developer options," and windows got to work right away. Rooted it no problem.
using xp is the best choice - you dont have to care about 32/64bit and the uac (user access control)
hope this helps you to get rid of the drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
I get this when I try to install drivers via install drivers.bat program.
Sent from my Galaxy Nexus using xda premium
as described in the linked post it's a good practice to move and rename kfu to c:\ that it is c:\kfu - it don't like spaces in pathname
the error message looks stange because "and" is no command - would try to redownload it
if it says "findstr" is not recognized as command then check your path varible - it should include c:\windows\system32
furthermore i use to run the batch files from the command prompt - cd to c:\kfu and type install_drivers.bat - the same with run.bat
It took three computers but I finally rooted the kindle.
Sent from my Kindle Fire using xda premium
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.
I am using my laptop for ADB currently, but I want to know if it is possible to run ADB through windows in a Virtual Machine? I have gotten to where I have ADB running and the VM reconizeds the phone but as soon as I type,
Code:
adb devices
There is no response. Side note: I am using VMware and am running Tvall's CM7 on my phone.
Edit: solved was a driver issue
adb works when drivers for adb were installed
did you install drivers from Android SDK Tools?
at second you need turn usb debugging on (settings/applications/development)
5[Strogino] said:
adb works when drivers for adb were installed
did you install drivers from Android SDK Tools?
at second you need turn usb debugging on (settings/applications/development)
Click to expand...
Click to collapse
Yes I know this. The virtual machine knows the device is there(ADB drivers are installed) but in cmd it doesn't work. USB debugging is on, another option is the wireless ADB from CM7, but I have no idea how that works. Thanks for the help.
acseazzu said:
Yes I know this. The virtual machine knows the device is there(ADB drivers are installed) but in cmd it doesn't work. USB debugging is on, another option is the wireless ADB from CM7, but I have no idea how that works. Thanks for the help.
Click to expand...
Click to collapse
When connecting phone through usb debugging there is 'Android USB Devices' section in Device Manager (My Computer / Manage / System Tools / Device Manager). Do you have this section while connecting?
Wireless adb application establishes connection via custom port and adb can use this port to communicate with phone.
5[Strogino] said:
When connecting phone through usb debugging there is 'Android USB Devices' section in Device Manager (My Computer / Manage / System Tools / Device Manager). Do you have this section while connecting?
Wireless adb application establishes connection via custom port and adb can use this port to communicate with phone.
Click to expand...
Click to collapse
In device Manager it has "Android Composite ADB Interface" and a "HTC Android Device" My VM connects to HTC Android device, not letting me connect to it in ADB. Before I connect my device and before it installed the drivers I installed the Google driver package from AndroidSDK. Thanks for your help.
How did you fix it?
acseazzu said:
In device Manager it has "Android Composite ADB Interface" and a "HTC Android Device" My VM connects to HTC Android device, not letting me connect to it in ADB. Before I connect my device and before it installed the drivers I installed the Google driver package from AndroidSDK. Thanks for your help.
Click to expand...
Click to collapse
So how did you end up fixing this? I want to connect my phone to the VM.
This is happening to me right now. I have a VM Windows 7, it can detect a "HTC Android Device" but the platform-tool command line cant detect my phone. Even with ADB USB drivers, platform-tools, as well as HTC-sync installed.
How did you fix it? Please tell me
kazzarok said:
So how did you end up fixing this? I want to connect my phone to the VM.
This is happening to me right now. I have a VM Windows 7, it can detect a "HTC Android Device" but the platform-tool command line cant detect my phone. Even with ADB USB drivers, platform-tools, as well as HTC-sync installed.
How did you fix it? Please tell me
Click to expand...
Click to collapse
I uninstalled all the drivers (with USBdeview) and instead of installing with the Google Driver I used the HTC one for MyTouch 3G. I think I installed the drivers before I plugged in the phone. And also what software are you using to run your VM?
acseazzu said:
I uninstalled all the drivers (with USBdeview) and instead of installing with the Google Driver I used the HTC one for MyTouch 3G. I think I installed the drivers before I plugged in the phone. And also what software are you using to run your VM?
Click to expand...
Click to collapse
I am using Oracle VM Virtualbox. Doing VM Windows 7 under Ubuntu 11.10.
I have been trying a few times in the VM Windows 7. I tried the lastest HTC Sync 3.0.0.0 as well as the older version 2.0.3.3 that worked when I was using full Windows 7.
But in VM, nothing works
The VM win 7 can detect a USB Composite Device, but it cant find the correct driver.
edit:
Oh my god!! hopefully you still havent read this post yet because I just got it working!
In the settings of the VM, theres an option to enable USB 2.0
But to enable that, we must install the Oracle VM VirtualBox Extension Pack
It works!
edit2:
but somehow the transfer speed is really slow...
i guess i will just install windows again dual boot it
Yay! Congrats if I helped at all please hit the thanks button.
Sent from my Dream/Sapphire using XDA
acseazzu said:
Yay! Congrats if I helped at all please hit the thanks button.
Sent from my Dream/Sapphire using XDA
Click to expand...
Click to collapse
Not until you tell me about your VM
I want to know that because at the moment the transfering and intallation of APK files in Oracle VM VirtualBox is utterly slow (comparing with my old Win7 days), I am interested in other alternative VM which might be faster.
I see you mentioned VMware in you first post, I went to their website (link) but I see a lot different products... can you tell me which one you used, can you please tell me more about your VM?
Thanks in adcance.
edit:
Hey there again, I fainlly got VMware working.
I went for VMware Player 4.0.2. But for Ubuntu 12.04, we need a custom patch the VMware before it can run gracefully.
Not I have got it running now, VMware is so much faster than Oracle VM.
Thanks for the suggestsion!
kazzarok said:
Not until you tell me about your VM
I want to know that because at the moment the transfering and intallation of APK files in Oracle VM VirtualBox is utterly slow (comparing with my old Win7 days), I am interested in other alternative VM which might be faster.
I see you mentioned VMware in you first post, I went to their website (link) but I see a lot different products... can you tell me which one you used, can you please tell me more about your VM?
Thanks in advance.
edit:
Hey there again, I fainlly got VMware working.
I went for VMware Player 4.0.2. But for Ubuntu 12.04, we need a custom patch the VMware before it can run gracefully.
Not I have got it running now, VMware is so much faster than Oracle VM.
Thanks for the suggestsion!
Click to expand...
Click to collapse
I personally use Workstation. But for me VMware is alot faster than Oracle VM VirtualBox. Glad I could help
adb driver won't connect
I'm running windows parrallel on my mac. On the windows side I have the samsung drivers downloaded but when I go to root my phone the command line says doesn't recognize. Anyone know away I can get drivers to recognize phone when running virtual on a mac?