From today onwards i decided to start with Android App Development,
So i started following some Android App Dev courses,
but while configuring "ADT" i encountered few problems, listed below:
The "Android SDK Manager" doesn't opens up, it only pop ups a loading box and then it never appears,
I tried using editing the android.bat file, doesn't works for me!
Also, The Android Virtual device is not working, when i try to make a virtual device,
Even after entering all necessary parameters, the "OK" button is still greyed/disabled.
Using:
Windows 8.1, JAVA RE 7, Update 71 (both 32 and 64bits)
Please help
Err0r_Infinity said:
From today onwards i decided to start with Android App Development,
So i started following some Android App Dev courses,
but while configuring "ADT" i encountered few problems, listed below:
The "Android SDK Manager" doesn't opens up, it only pop ups a loading box and then it never appears,
I tried using editing the android.bat file, doesn't works for me!
Also, The Android Virtual device is not working, when i try to make a virtual device,
Even after entering all necessary parameters, the "OK" button is still greyed/disabled.
Using:
Windows 8.1, JAVA RE 7, Update 71 (both 32 and 64bits)
Please help
Click to expand...
Click to collapse
need more info? see logs for detailed information
Your virtual devices are not working maybe, because u dont downloaded sdk version from virtual manager ? Try to update and download all stuff that u dont have, and then try .
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.
(Moved from development forum, newb root thread)
I recently received my phone back from a HTC repair. I hadn't used it til today as I was waiting for froyd 1.5 to come out before rooting it and setting it up. Today I switched it on and it asked me if I wanted to update the software, I clicked no. Then I followed the steps in the OP but had problems in step 5 : everytime I typed anything (including "su") and hit enter I had a message saying "denied" or words to that effect, despite the UniversalAndroot program giving the "woot rooted" message.
This is the part where I might have done something stupid - I decided to let the phone update itself to the latest software, and then I was planning to run the UniversalAndroot again. I thought that maybe UA had been tested on the latest official HTC stuff but not whatever 2.1 but not fully updated version that mine had come back from repair with. It went to the update screen and the progress bar completed, it tried to reboot but just got stuck on the white boot screen with the green HTC logo. If I pull the battery out and start again it just hangs at the same screen.
I can get the 2.73.405.5 WWE RUU to see the phone when in fastboot, but when I try to update it it eventually gives me error 140 "bootloader version error".
I tried to load it through HBOOT using kazuni's technique in his thread "A way of flashing the RUU rom extract" (sorry, it won't let me paste a link to the actual thread) but it says "main version is older, update fail". Do I need to send it off to HTC again? I just got it back! Will they be able to tell what broke it and refuse to fix it?
Many many thanks
Try the 2.1 downgrade in my sig below.
Please could you explain "The recovery can be flashed via running 'runindos.bat'."? I assume I need to install this adb program that people keep mentioning?
Also what is the goal here? To upgrade my phone to 2.1 (which was already on from the HTC repair, the OTA update just said something about adding g-sensor calibration tool) to then root it or to downgrade my phone to 1.5 to root?
Many thanks!
Ah, just seen adb guide on villain forums. OK, I'll follow the guide to get adb installed, put your recovery files in the /tools folder, but then how exactly do I flash the recovery? Simply by typing runindos.bat in cmd whilst in the correct folder?
Ah, I see, I just run the batch file from your recovery download. Sorry for all the dumb questions! I ran this with my phone on fastboot usb but it said this :
adb server is out of date. killing...
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
"Files copied and permissions set, rebooting HTC Andriod 2.1"
"Your phone will now reboot into normal mode, then reboot into recovery mode. I
f it does not reboot the second time, wait 10 minutes and manually reboot and be
gin again."
error: device not found
As far as I can tell nothing happened on my phone. I assume my usb drivers are fine as the RUU was able to begin updating before it gave me the 140 version error. Any ideas?
It's the ADB drivers, what OS are you using?
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
HairyBones said:
I am using Windows 7. I thought i read that the latest version of htc sync had drivers fully compatible with win 7 and the RUU seems to see it fine once I selected 'my htc' drivers under adb in device manager. I am confused!
Click to expand...
Click to collapse
You may want to build an XP workstation eitha virtual or physical. Don't be alarmed. Yes, the latest version of HTC Sync does contain the drivers. However, they some what don't work for majority of users. Sorry.
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
HairyBones said:
Just did a quick google - will http://www.microsoft.com/windows/virtual-pc/download.aspx work?
Click to expand...
Click to collapse
virtual box - http://www.virtualbox.org/
vmware player - http://www.vmware.com/products/player
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
HairyBones said:
Eek - I need to get an xp install disc and set it up like I was loading it onto an actual PC? The microsoft tool within win 7 definitely wouldn't work?
Click to expand...
Click to collapse
Yeh, to install XP you will need an install disk, unless you download XP Trial version VHD. This is the trial version from Microsoft in virtual machine mode.
http://www.microsoft.com/downloads/...90-958F-4B64-B5F1-73D0A413C8EF&displaylang=en
Windows XP Mode with Windows Virtual PC, available for Windows 7 editions Professional, Enterprise, and Ultimate, provides a licensed virtual Windows XP Professional environment for compatibility with applications not compatible with Windows 7. Windows Virtual PC supports USB attachment, therefor supporting direct connection of USB devices to the virtual Windows XP environment.
For information and to download Windows XP Mode or Windows Virtual PC visit the product page microsoft.com/windows/virtual-pc/default.aspx
Brandon
Windows Outreach Team- IT Pro
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.
hello xda,..
i was having win7 on ma laptop..recently i have upgraded it to win8 .. my screen clarity has decreased and looks somewhat blur..right now i don have drivers cdto install..so is there any other ways to solve my issue?? pls reply...thanks
my laptop is asus (x5dc)
If you haven't installed the drivers, then your screen probably isn't set to the correct resolution. Go into the screen settings and check that the resolution matches the specs of your laptop.
Keep in mind, without the proper drivers installed, you may not be able to change the resolution.
If you can find the drivers cd, go to asus web site and download a copy of the video drivers.
Move your cursor to the bottom left of the screen on desktop so the little start square appears, right click it and in the menu which appears click "device manager".
This will open the device manager window. In the list that appears will be an option called "display adaptors". Click the arrow next to it to enlarge the options. It should then list what graphics chips are available on the system (in my case on this laptop "Intel (R) HD Graphics 4000", on my desktop NVidia GTX460 and some AMD integrated chipset).
Right click whichever appears (if 2 do this twice, once for each, but do it 1 at a time). Click update driver software. Click "search automatically for driver software". Unless the laptop is older than I think, windows should be able to go off and locate the correct driver for you and install it, you will need an internet connection.
Once that is done, reboot and then go to desktop (you must not skip the reboot). Right click the desktop > screen resolution. In the window which appears set the resolution dropdown box to 1366 * 768, anything else is incorrect for your laptop. The screen might flash a bit as it resizes, thats normal.
Running windows update fully may also update your drivers, its a good idea to try the method above first and then run windows update anyway.
Failing that. ASUS have all the drivers available here: http://support.asus.com/Download.aspx?SLanguage=en&m=X5DC&os=17
thanks... but wen m trying to install the drivers it show's .net framework is needed...and when m installing .netframework it show's d same...and its not installing..
Sent from my A116 using XDA Premium HD app
darshan dazzGeEk said:
thanks... but wen m trying to install the drivers it show's .net framework is needed...and when m installing .netframework it show's d same...and its not installing..
Sent from my A116 using XDA Premium HD app
Click to expand...
Click to collapse
There is something seriously wrong with your windows 8 install if the drivers are claiming to need the .net framework and the .net framework won't install, its built into windows 8.
But if you want to try a manual install of the .net framework:
http://www.microsoft.com/en-us/download/details.aspx?id=21 .NET 3.5
http://www.microsoft.com/en-us/download/details.aspx?id=17718 .NET 4
http://www.microsoft.com/en-us/download/details.aspx?id=30653 .NET4.5 but I doubt required.
But before trying any of those 3 links (which are in the order I would try them), run windows update. The full update, every single important and recommended update. Will probably take hours (on my internet it will actually take 2 days....) but to me it sounds like there is something not right on your system, windows update should fix a few things (like lack of .NET and possibly drivers too) and you can go from there.
my windows 10 PC start , sttings ,windows 10 apps not opening , edge browser shows class not registered
reset pc
Gokul Rajan said:
my windows 10 PC start , sttings ,windows 10 apps not opening , edge browser shows class not registered
Click to expand...
Click to collapse
Since the only constructive response was "Reset your PC" without telling you how to do so even though you say "Settings and Windows 10 apps not opening", I will do that person one better and actually give you instructions for resetting.
Reboot your machine, at the login screen, instead of typing your password or PIN, hold shift and while holding shift press Restart from the Login screen (click the power button and choose Restart). Continue holding shift and it will bring you into the Windows Recovery Environment. Choose Troubleshooting, Reset This PC.
@ahmadus The user wouldn't be able to reset his PC without getting into Recovery Environment. As the Reset this PC function is exposed through the settings app that OP says does not open. In this case, the user may not know how to enter the Recovery Environment from alternative means. If you're going to provide help, actually provide constructive help.
@ShadowEO I thought reset pc is the easiest thing to do on windows 10.
ahmadus said:
@ShadowEO I thought reset pc is the easiest thing to do on windows 10.
Click to expand...
Click to collapse
It is, but it's only easy if you can access the Recovery Environment to start the process. The good news is that you can start the process using a Windows 10 Installation disc (either USB or DVD) by choosing "Repair your computer" instead of "Install" when the installer starts up.
Latest Version
Try this version: http://www.softolite.com/windows-10-lite/
This is the official trial version with the latest build.
Wrong, you should ONLY download media from sources you trust, such as the official Windows 10 media creation tool or ISOs available at https://www.microsoft.com/en-us/software-download/windows10, THIS is the official URL to download Windows installation media. Also @CarlRock, all versions of Windows are trials until they're licensed, that blog is not the official source of ANYTHING Windows related.
You should also NEVER use a "lite" version of Windows unless you yourself built it, or you understand both what was removed and the consequences for removing that Windows component. Many users on the Windows subreddit go removing components without a full understanding of what they do or their full purpose in the OS, then come and complain that the system isn't working right.
Just use Windows as it was meant to be used. If you don't need a feature, don't configure it, or just plain don't use it. Dont just eviscerate it from the system without a thought to stability.