I installed the Win 10 drivers,
I installed ADB and its DLLs and fastboot.
I cannot install the Java run time as it doesn't
know Windows 10,
The VMware guest does see the the an droid phone
as an MTP device.
adb devices reports nothing
with the phone running adbwireless
adb connect [ip address] also fails.
Is it just Win 10 isn't ready for prime time yet?
Or is there something else I can try?
Update: Fastboot boot does see the device from the guest.
maybe it is a driver or DLL issue?
Don't have any issues with adb or fastboot on Windows 10 here. I have Java 8_35 installed. Don't know why you can't either.
I guess I was in too much of a hurry
After restarting, and reconnecting the phone, it decided to load new drivers.
ADB and fastboot both appear to work as expected.
Java still wont install, but doesn't seem to need either.
Maybe the Java requirement of the android SDK
is for other things?
thanks for replying
fuzzynco said:
After restarting, and reconnecting the phone, it decided to load new drivers.
ADB and fastboot both appear to work as expected.
Java still wont install, but doesn't seem to need either.
Maybe the Java requirement of the android SDK
is for other things?
thanks for replying
Click to expand...
Click to collapse
You on the latest preview build? It thinks mine is Windows 8.1
ye,s, it thinks mine is too (Win 8.1)
I guess Java isn't ready for Win 10
Related
It seems that i am not able to get ADB to work on any of the 2.1 versions i tried.
I installed, uninstalled, reinstalled the Dell PC suite.
The phone is in USB debugging mode.
My device manager is seeing "Android ADB interface" under Android phone but doing "adb devices" is showing no connected devices.
I have an at&t locked phone which i upgraded to the O2 8105 release and then downgraded back to 6941 2.1 beta release.
I had no luck getting ADB to work on either firmwares. i never tested on 1.6.
Running windows 7 64bit and also tried on Windows 7 32bit.
Nothing works.
Anyone has any idea how to get ADB working?
I am starting to think that at&t somehow blocked ADB so we wont be able to install 3rd party APK's and it is hardware blocked. My Streak is two days old so i got it from recent batch.
End task your adb.exe in task manager, locate adeproxy within the dell suite software and use that in place of adb.exe. this allowed me to get the sideload app working on 1.6.
THANKS!!!
that works. i would never figured it out myself.
So is dell doing this on purpose?
Dunno if its on purpose, some kind of driver conflict with adb itself.
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
Make sure that you've mounted USB as "None", you can do so by pulling down the notification bar. Hope that helps!
fightingcrest said:
Here's the situation: Couldn't get retainroot working on previous occasion on my 64-bit system. Installed SDK on 32bit Win 7 system and was able to use both beforeupdate.bat and afterupdate.bat. Now...when trying to use any of the MODS available, adb cann't recognize my device and I get error messages like "psneuter failed to execute properly". I've done my searches on this subject in XDA but i don't think anyone else's experience is the same since the Atrix is a bit different. This is the first time i've had so much issues with adb. If anyone has any clue whats going on. I've all but given up on this device. I'm 14 days in with it and all headaches.
Click to expand...
Click to collapse
make sure usb debugging is ON, set usb connection to NONE. I'm assuming you have sdk installed in c:\ of computer. Then go to cmd prompt and type: "cd c:\android-sdk-windows\platform-tools" [enter]
Then, type: "adb devices" [enter]
Should detect device, or something is wrong.
Hell, just go install the CWM and install the mods that way. A lot of them are updated to now work with CWM. See here: http://forum.xda-developers.com/showthread.php?t=1019143
If anyone has tried using WebOSQuickInstall you will know that the novacom drivers it tries to download fail on lion, so here are the drivers from the webos 3.0.2 SDK which should work (works on my late 2009 MacBook running lion) (use at own risk)
Download
Edit: before I get into trouble for these links I have decided to pull them. The best way to get them us via the webos sdk
Hope this helps
That worked! Thanks so much, no more rebooting into Bootcamp for me.
Thanks for that! Works great!
Eventhough I found the Novacom driver installer inside the SDK package, and installed it just fine, still I get the same message from Webos Quick Installer (4.2.3) "No devices connected. Please connect a device to continue". My device is in Developer Mode (HP Pre 3). I've tried putting it in normal mode and back to dev mode again, same thing. I restarted my mac twice, same thing. Does anyone have any idea why is this happening? I tried the whole process on my brother's laptop (win xp professional), and works just fine. So, what am doing wrong?
Plug it in but don't put it in usb mode
Sent from my HTC Sensation Z710e using XDA App
thanks for that !!
Can you repost the driver?
please update the first link
webos sdk has a big size just for a one little driver
Here's a fix for the driver:
After a failed install...
vim `which start-novacom`
add an "F" after the -w... so the command looks now like:
sudo launchctl load -wF /Library/LaunchDaemons/com.palm.novacomd
then run start-novacom, and novacomd will load and things will work.
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Looking for working adb Windows drivers for Huawei Y300-0151 I've tried at least 5 versions on a Vista, 7 and 10 OS (all 64x) machines and none allow fastboot to see my phone. I'm currently using Windows 10 Pro 64.
Thanks.
Doesn't anyone know where I can get a set of drivers for Windows 10 or even an older OS that will allow Fastboot.exe to see my device? I have my bootloader unlock key, I just need to be able to use it!
Thanks.
Well I found a working set of tools that sees my phone. Now all I need is a back-up of the stock rom in case I need it. Anyone know where I can get a Y300-0151V100R001C557B184 official firmware?
Thanks