I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
SG_Shadow said:
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problems. I've downloaded the sdk and ran the sdk setup.exe and downloaded all the latest files, and of course the usb driver. I was able to successfully install the driver and was able to connect my G1 for file transfer. I've followed the guide info to the letter but for some strange reason I get the following:
Code:
* daemon not running. starting it now *
* daemon started successfully *
error: device not found
I've already tried uninstalling the newest driver and installing the working one from my pc, then I tried downloading a driver that was listed by a user in this thread. Still no luck. Any advice would be greatly appreciated!
Click to expand...
Click to collapse
plug your phone in
get working drivers
install linux, it works better
I already have my pc setup with adb. It appears to be working just fine. I'm trying to setup adb on my laptop and is running into all types of problem
Click to expand...
Click to collapse
[*]plug your phone in
[*]get working drivers
[*]install linux, it works better
Click to expand...
Click to collapse
u forgot a step.
[*]post in the correct forum
Firerat said:
plug your phone in
get working drivers
install linux, it works better
Click to expand...
Click to collapse
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Daneshm90 said:
u forgot a step.
[*]post in the correct forum
Click to expand...
Click to collapse
Fail!
SG_Shadow said:
1) Done [Don't insult me!]
2) Tried 3 different drivers. All allowed me to connect my G1 to transfer files, but not ADB.
3) ...shouldn't have to install linux. My pc (running windows abviously) works just fine. My laptop, running windows, should work the same.
Thanks for the assistance though...
Fail!
Click to expand...
Click to collapse
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
This IS in the wrong forum.
Moved.
Firerat said:
read the adb for dummies thread, post in that thread...........................
and
your welcome.
would you like me to wipe your nose as well?
Click to expand...
Click to collapse
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
SG_Shadow said:
I really wouldn't except this behavior from you, but I see we all fall from grace every now and again. I've posted in that thread already, no one can seem to come up with an intelligent response. I followed all the instructions in both adb help threads for proper installation on my laptop. If you don't know the answer to what I'm seeking, I would honestly prefer you not to reply at all. Don't assume I'm the typical xda idiot, assume I'm the most intelligent person you've ever spoke to, then go from there with your next reply.
Click to expand...
Click to collapse
you posted a couple of hours ago, duplicating posts might be considered spam
you didn't really give any useful information in your post(s)
and if I were to assume your were, then this is just some boring role play thing at a job interview or something, as you wouldn't really need anyones help on this.
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
ivanmmj said:
Everyone, Chill it.
We don't need a flame war.
Check your firewall. Make sure it's not blocking the connection. Also, are you using the same USB cord on both machines?
Click to expand...
Click to collapse
Thank you for trying to "actually" assist me. I am using the exact same usb cable on purpose to rule that out as a reason. I've also recently update both computers to the latest norton antivirus. Like I stated the drivers install on the laptop and I'm able to connect the G1 for file transfers, so I assume the driver is working but when I type in adb device or adb shell in cmd, I get the no device msg. I'm really stumped with this one...
*Update* My norton did remove adb.exe from windows\system32 on both computers, but I was able to restore that file on both. Like I said, my pc works just fine, laptop no good...
And point 3
Install linux ( ubuntu 10.4 )
Just give it 10gb
It will eliminate hardware faults as being the problem
The android developer has a tutorial for 10.4, so it should be easy
( no need for drivers, aparently 10.4 ships with the android udev rule )
the driver for file transfer isnt the same as the driver for adb....so your logic is flawed
seriously tho, use linux...wubi is pretty good now and u only need 4-10gb if u are only using it for android stuff
in my experience, windows, especially where norton is used, randomly breaks adb
The file transfer is done using the standard windows mass storage driver, not an android specific driver. Even if it's the same norton, try disabling it and see what happens. Also, trying removing the driver completely and reinstalling it again. I've had the issue happen also only when in windows and it's always something random.
virtualbox _should_ ( I think ) let you 'see' the Android Phone regardless of the drivers being installed on the Windows host
But, I have not tested that
Did you ever get this to work, I have the same issue?
I'm having the same issue, I'm trying to use ADB with my TF300T from a Windows 7 64 bit system. Always get the error adb error.
I have a couple of questions will this work correctly with a 64bit O.S?
Also the part of the instructions that reference SDCARD are they talking about the directory on my ASUS /sdcard/ or are they talking about the physical card?
Just need to know does it require you to have a sdcard in the ASUS to use adb?
May sound like fundamental questions to a lot of you, however I have combed through these forums as well as others all over the web, and the majority of instructions seem to be lacking the basics.
Thank you,
I have Ubuntu at work should I run ADB through this?
I have Ubuntu at work
It's a bit of a process according to the instructions that I have on the
screen right now to setup ADB through this, is there any gotchas that I should
know about before attempting this?
This is running on a VM on one of my servers. What I'm looking for is any known compatibility issues with versions of ADB and the Asus TF300T running .26
Thanks in advance.
Nordis
Related
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
beyondinferno said:
the sticky wiki for guides at the top of the front page....
try to look around a little before starting new threads.
Click to expand...
Click to collapse
Thanks for your help...I did look around but I still can't get it to work. I've been through quite a few threads. I don't know if I'm missing something somewhere or what.
is your problem your computer not seeing the phone?
i RUU'd my phone earlier today to test out something i did, but then i found out that adb couldn't connect anymore. i'm still trying to figure it out.
Exactly what are ya having problems with?
http://forum.xda-developers.com/showthread.php?t=502010
1. HTC Sync installed?
2. Android SDK downloaded?
3. Debugging enabled on the phone?
4. is ADB showing up in the Device manager?
5. Check this thread out dealing with x64 drivers
http://forum.xda-developers.com/showthread.php?t=560962
Hmmm..
I have Win7 64bit too
I think I just downloaded the newest Android SDK and HtcSync for the Eris. It
works fine for me. What exactly is the issue? You have the phone in debug mode or whatever mode right?
some folks have used PdaNet
http://www.junefabrics.com/android/download.php
first off, I can't get Sync to work at all no matter which version I've tried. Then the drivers won't load for sdk. it just seems like nothing is working together at all.
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
justinisyoung said:
alright, i figured it out.
uninstall HTC Sync and the HTC Drivers.
reinstall.
done.
Click to expand...
Click to collapse
yeah just make sure you use the newest HTC Sync for the Eris!
just out of curiosity why the eris? am i going to have issues later down the road?
DanWalker said:
I have tried every process I can find in the forum regarding rooting and ADB but I cannot seem to figure this out. I would like to think that I am computer literate and that I know my way around pretty well but somehow this escapes me. I am running Windows 7 64 bit and can't seem to get anything right as far as this process goes.
Is there a rooting/adb for dummies section that someone can point me to?
Click to expand...
Click to collapse
Alright... what's your main problem? Are you not able to get the ADB driver to work with your phone in Windows 7 64 bit -- if so, do know that it is possible, because I have it working fine on my computer (Win 7 64B).
If ADB driver situation is your problem, do as follows:
1. Download the file below (to desktop for easy access - This is the Vista 64 bit Drivers)
2. Unzip
3. Go to Device Manager
4. Find ADB (It should come up as ADB with a Yellow Exclamation mark next to it)
5. Right click on it, choose update driver
6. When it asks you to auto find the driver or browse for the driver -- choose BROWSE.
7. Set the path to where you downloaded the file, and then click next.
8. If done correctly, you should see a window pop up that says "Successfully installed My HTC driver".
ADB will work after that is complete. To test, open CMD - go to androidsdk\tools folder, and then run adb devices (If serial # appears, there you have it).
Also with the method above, this will allow the HTC Sync application to work as well.
Source: ME, tested extensively and more than once.
DanWalker said:
just out of curiosity why the eris? am i going to have issues later down the road?
Click to expand...
Click to collapse
HTC Sync for the Hero was released before Win7, so the Vista drivers will work but you have to jump through some hoops.
Now the Eris version is the same HTC Sync but it has drivers for Windows 7, it is the same software but is bundled with newer drivers.
Roger that guys, thanks for the help. I will attempt tonight when I get back to my computer.
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
rlaxton said:
yeah they took out the packages of the SDK, so you have to add them in as needed.
I have a 2nd Win7 box that's an Android virgin, I will try and run through the install tonight(off at 5pm PST)when I get home and I'll document the install.
hang in there.
Click to expand...
Click to collapse
That would be awesome, I'm at the point where I am just about to give up. I have never been so frustrated with a computer. This is the first Windows 7 system I have done anything with and I already don't like it.
DanWalker said:
Ok just got home and am doing the suggested things, after installing the SDK it wants me to install packages and when I choose cancel, windows says the program was not installed correctly. what do i need to install?!
Also no ADB in device manager!
Click to expand...
Click to collapse
Install packages? What? Weird, the Android SDK is natively 32 bit, but will work in Windows 7 64 BIT (That's what I'm running now).
Alright, steps to take:
1. Uninstall/remove everything you did before.
2. Grab the Windows Android SDK -- download it (to the desktop is fine)
3. UNZIP/Extract the SDK
4. Drag the Android SDK to the root of your drive (Local Disk C: )
5. For easy access purposes, RENAME the Android SDK from what you see to something like: androidsdk
6. Open Command Prompt
7. Verify that you can get to the "androidsdk" directory by running the command: cd androidsdk\tools
8. If you can get there -- then good, so far.
9. Now to test "adb" -- Have your phone connected to the PC.
10. While still in command prompt and STILL in the c:\androidsdk\tools: dir... run command: adb devices
11. This should return your Serial #
12. If your serial # shows up, then make sure you can run the command adb shell and see if you get the # sign, which indicates that you are rooted -- If not, then you need to begin the process of rooting your phone.
Also, if ADB doesn't work after this point, do what I told you earlier, I can guarantee that it does work, because I actually did it this morning on my work computer (Which is Windows 7 64 Bit).
Good luck, report back.
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer. I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
via adb -> Requires a custom recovery (with test-keys)
Code:
Copy recovery-RA-heroc-v1.6.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
None of that seems to work lol.
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
DanWalker said:
Holy crap it looks like it worked!! Thanks Pseudo! Now if I could only get my damn phone to find Sync I'd be all set.
Still can't get sync to register with phone but that's no biggie. But have a small issue that I dunno where to look to find an answer.
Click to expand...
Click to collapse
First off, no problem for the help -- glad it worked. What ROM are you currently running, that would be helpful in solving your sync issue.
DanWalker said:
I'm trying to update my recovery from 1.5.2 to 1.6.2 and can't seem to follow the directions appropriately.
Click to expand...
Click to collapse
Alright, lets begin - To upgrade to RA 1.6.2, (You have to be in recovery mode (Home + Power) -- and also have your phone connected to the PC). Then do as follows:
1. Download the 1.6.2 file
2. Copy or move it to your androidsdk\tools folder
3. Run commands below:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Code:
C:\AndroidSDK\tools>adb shell
Code:
mount -a
You'll probably get the next line below -- that's okay.
Code:
mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: No such file or directory
Keep going...
Code:
flash_image recovery /sdcard/recovery-RA-heroc-v1.6.2.img
After you do this, the shell should return #, if it does, then run:
Code:
reboot recovery
Now verify that your recovery says 1.6.2.
Good luck.
thatguythatdid said:
So since we're on the subject does anyone know how to set up the drivers for linux mint kde? I'm brand new to linux and I've managed to do some things but that is just one thing that i cant do so far and after almost a day pf searching this forum and others i just cant seem to get it
Click to expand...
Click to collapse
Well, since you've asked a good question, I shall direct you in the right direction. Linux Mint is a derivative of Ubuntu, so this guide should work for you., however do note that I have not tested this in Linux Mint, as I currently run Ubuntu 9.10, but you should be okay.
Go HERE and bookmark this page for reference, it has some good stuff -- Now this guide is not directly for our phones (CDMA HERO), however the directions, if followed correctly... DO WORK and have been tested by me (did this last night) with successful results.
When you get to the web page, start at "Generic Linux Instructions". Also, when you get to the heading "Set up ubuntu to recognize your phone, and the adb/fastboot commands in the terminal" -- step 4 will ask you to create an empty file, use the Ubuntu 9.10 format and NOT the older versions, again this format should work in the latest version of Linux Mint.
Hope that helps. Also, if have problems or want a step by step tutorial (pending how "new" to Linux you are), just ask me or PM me, I'll write one up.
Been at it for 2h now and i just can't seem to make it work, ive installed the latest nookie froyo on the internal memory of my nook and i just can't seem to get the market on it, i tried with a guide from http://forum.androidcentral.com/bar...ion-install-nookie-froyo-internal-memory.html
But everytime i try the adb commands i get a device not found error and i can't seem to fix this problem, i have tried to install the nook usb drivers but i still get the same error, is there any easier or other way of getting it?
Thanks
Kris
Anybody?? A tablet with no market and no youtube makes it kind of useless....
Gunner86 said:
Anybody?? A tablet with no market and no youtube makes it kind of useless....
Click to expand...
Click to collapse
Yo. nookdevs dot com ADB_Over_USB
This is my second post of eight minimum. Won't let me paste a hyperlink.
Also, scan the developement section and look for some of the market zip files for Froyo.
Once you get on the market, download ADB wireless. I find it better than ADB over USB.
NookDevs also has very good tips for Froyo and where to download what.
For some reason when you simply install JUST the install.exe it doesn't work (well it didn't for me atleast) I had to also run the DPInst64.exe since I am on Windows 7 64-Bit OS. After runing the DPInst64.exe and letting it install I was able to use ADB over USB.
If you are running a 32-Bit OS DO NOT run the DPInst64.exe - Use the DPInst.exe instead.
I had MAJOR issue getting ADB to work.
All my info came from this thread:
http://forum.xda-developers.com/showthread.php?t=910008
You really need to read and re-read this and make sure you follow the exact instructions and it will work.
The problem that caused me some issues was the USB Debugging check mark was not on. But that was a problem with Auto-Nooter 3.0, you are using Froyo.
I can confirm that once the ADB drivers are installed with Auto-Nooter, they will automatically be okay when you are in Froyo (which I am now). I did not have to redo anything.
I spent several hours uninstalling/reinstalling devices and usb ports, etc in Windows Device Manager. Both on Vista 32 bit and Windows 7 64 bit. They all work fine now simply by following that thread.
Hey all,
I managed to brick my Nook HD+ a few month ago (see previous threads). The EMMC partitions are broken and I cant access them.
So, I noticed a few ROMS that work of a SD Card. The only problem is, the installation seems to need to store the ROM on the internal EMMC in order to install it.
Is there a way round this?
Cheers
There is an emmc-less Rom you can find the link from the following thread.
http://forum.xda-developers.com/showthread.php?t=2544606
Direct link
http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
Thanks for the reply.
I'm struggling with the adb push part and adb just wont work, ive tried
http://forum.xda-developers.com/showthread.php?t=2336088
http://rhuno.com/flashblog/2013/03/17/getting-the-nook-hd-recognized-by-adb/
the driver installs successfully and i still cant see my nook via adb. Is there anything i could be missing.
smurfster said:
Thanks for the reply.
I'm struggling with the adb push part and adb just wont work, ive tried
http://forum.xda-developers.com/showthread.php?t=2336088
http://rhuno.com/flashblog/2013/03/17/getting-the-nook-hd-recognized-by-adb/
the driver installs successfully and i still cant see my nook via adb. Is there anything i could be missing.
Click to expand...
Click to collapse
What OS are you running? I had no issues once I did step 7 myself on Windows. On Linux it really depends on the distro and I don't use a Mac so not sure.
smurfster said:
Thanks for the reply.
Click to expand...
Click to collapse
You should really hit the Thanks Button for him instead of just saying thanks
jpisini said:
What OS are you running? I had no issues once I did step 7 myself on Windows. On Linux it really depends on the distro and I don't use a Mac so not sure.
Click to expand...
Click to collapse
tried a different computer and still no luck. I use windows 7 pro
someone mentioned I need the google usb driver. But how do I install it? it wont install via the right click > install option
Maybe try https://nookdeveloper.zendesk.com/entries/21943338-nook-developer-start-up-guide#top
Well I'm stuck nothing seems to work
Just a quick note.
Be sure to use v1.0.31 of adb or greater, or it will not see your device.
Also, in my bootimg_tools_ovation are the files necessary to get adb working in linux.
(the "hidden" .android folder gets copied to home, and the rules file to /etc/udev).
Someone really should make a live linux usb/flash image with working adb for the nook. (Just boot from usb key and have working adb)
Wouldn't be that difficult.
Ouya SuperScript
By TehCrucible
v0.1
INTRODUCTION
So I originally wrote this batch script to simplify and combine some of the most frequently used tweaks on the forums for my own sake, to speed up my tinkering with the Ouya but I've decided to clean it up and upload it in case anyone else wants to use it.
This script is designed as a "one-click" modification tool for a stock Ouya on the latest firmware. Please read this guide carefully.
I ACCEPT NO RESPONSIBILITY FOR ANY DAMAGE OR DATA LOSS. This script is built on the work of many others much smarter than myself and be sure to check the credits.
SO WHAT DOES IT DO?
In a nutshell:
- Install Clockworkmod Recovery
- Root Ouya
- Install Xposed Framework
- Install Google Play Store
WHAT DO I NEED?
- A Windows PC. I have included drivers for both x86 and x64.
- A Micro USB cable.
INSTALLATION OVERVIEW
1. Update your Ouya to latest stock firmware
2. Install ADB drivers
3. Run the script
4. Play some games!
There's a more detailed step-by-step in the included README.txt file.
KNOWN ISSUES
- None
CREDITS & THANKS
WonderEkin
mybook4
elmerohueso
fatesausage
DOWNLOAD
Here
Thanks a lot for this. A lo of people have been asking about an automated method to get the play store running on the OUYA...
Great works. I just think of root my ouya....
A quick update:
It's working. I'm on the latest firmaware which is JZO54L-OUYA, kernel version 3.1.10-g780994a. Completely stock, but I had already rooted my OUYA.
Anyway, I enabled the Wireless ADB which will instantly show you the ip and port, installed the drivers for 64bit. Then open CMD and type: adb connect "iport"
Then I ran the superscript and everything went fine.
Hope this helps. I didn't even have to connect with a wire.
But I guess if you wanna install the CWM recovery you should be connected with a wire...
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
Did you install the drivers right? If yes, then you should open the folder where you extracted your files and right click while holding shift then choose open CMD here. Then write: adb devices
If your device is there, it will give you an output of the IMEI and name of device
From there, you can then tell us what the error is and hopefully we can resolve it...
zmelkoow said:
Hello guys!
I can see the Ouya in Device list in Control panel but I can't connect it in SuperScript. Any ideas?
THX
Click to expand...
Click to collapse
that happened to me yesterday, but I overcame it by have my computer plugged into the Ouya then reboot the ouya and as soon as the computer recognized it started the script and it worked.
but I have an issue too
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesnt recognize the ouya....
unkoil said:
So I can run the script everything works except getting the recovery installed. the command prompt acts like it successfully installed the recovery then the Ouya proceeds to reboot into recovery mode. When that happens I get this menu? Nothing happens when I push any buttons on my keyboard. This doesn't look like a custom recovery.
Click to expand...
Click to collapse
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
TRMB said:
I have tried this many times, did a factory reset and started fresh however even after updating the device driver it doesn't recognize the ouya....
Click to expand...
Click to collapse
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.
Which version of windows are you on? Is it Windows 8 or 8.1? Do you know how to disable driver signature verification?
Also, what does it say when you connect? Just nothing, or not recognized or what? You can try the adb wireless, go into settings/development on the ouya and activate it. Then open CMD from the extracted folder and type adb connect "ip : port" then check by typing "adb devices". Let us know what happens after that.[/QUOTE]
I have tried both from my windows 7 computer and 8.1 laptop. It showed up just as you said "missing driver", sent it to the drivers part of SS to get the driver, it said it installed but when i run the SS and hit option "1" it comes up blank...
ahmadshawki said:
No it doesn't :angel:.
I think I had the recovery installed when I first got the device a long time ago and I used the manual method in this thread, but I'm not sure that it works any more. Also do you have a wired or wireless keyboard? By the way only the Bluetooth keyboard doesn't work. May be if you can install the recovery from that thread, then you can proceed to the next step. One last thing, I don't think you will need the recovery except if you want to install CM or something. Other than that, I never used it before.
I am having the same issue but not only with this method, I have also tried to install CWM with oneclicks auto and manual method to no avail.....
any suggestions?
Click to expand...
Click to collapse
always says it installed but will only boot into stock recovery
TRMB said:
always says it installed but will only boot into stock recovery
Click to expand...
Click to collapse
I can see from your posts that you tried everything and I'm so sorry that I'm just a user and not a developer or something. May be you can try sideloading terminal and try CWM manually (if you haven't already) or sideload ROM Toolbox and try the flash recovery option.
That's all I got. But if I were you, I won't bother about the CWM at all. It's useless.
As for the Play store, try the mod that I attached in my reply and let me know if this one works for you...
Unfortunately the link is not working. Is it possible to update it, please?
What I do if my micro usb is broken :/. I only have wireless adb
.. nice .. now my ouya will run again .. thanks
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
vinirockman said:
I already tried everything but I can't make this work... I installed every single drive in every single way.
The best screenshot of the whole situation is on attachment. SuperScript simply doesn't recognize OUYA with default drivers, neither provided drivers (or any of its variation like "composite adb" or something like that. The "List of devices attached" always return empty, even when provided drivers installed (signature deactivated and everything else). As readme says, when SuperScript doesn't recognize, it returns "error: device not found" every time that I try something...
This SuperScript seems great to start things on my my untouched and default OUYA... but I'm honestly out of options.
Click to expand...
Click to collapse
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
vinirockman said:
Problem solved. It is Windows Drivers issue. S-Config did a great job explaining how you should do this HERE. I hope it helps people who got stuck. SuperScript did work, I did installed CWM but I was not able to navigate (neither thru bluetooth usb full keyboard). I'm going to try to figure out what I'm missing later. As I can see, S-Config's website is fully updated... I do highly recommend read there who is going to do anything with ouya.
Click to expand...
Click to collapse
.. CWM need wired usb keyboard no navigate .. i don't remember if it can do it via bluetooth
I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?
@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Thanks for the reply. Unfortunately that seems to have done nothing
I'd go w/ uninstall all other drivers first, change cables and see what happens.
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...
efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.
OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.
morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk
FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.
Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.
Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.