Update 08/2013:
tonyp said:
Okay, another project I can close down.
As some of you might know koush has built a universal adb driver a while back.
I sent him a pull request a week ago of my work for the P990/P999:
https://github.com/koush/UniversalAdbDriver/commit/a04fd56de48dc7a7cd0e20ece78ed19274b2bc5d
He merged it and did a rebuild of the driver, you can download it here:
http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi
Source code: https://github.com/koush/UniversalAdbDriver
There are a mainly two advantages by using it:
- it is a universal driver for many Android devices (all Nexus + several HTC, Samsung and Motorola phones)
- you don't need to disable driver signature enforcement on Win 8
If you only got one device then you won't need it at all of course, you can just use the official driver by LG.
This driver was built (and needed) before LG released ICS (and the updated driver for ICS+ ROMs).
If your device ID is missing send koush a pull request, the linked one I posted above should tell you the proper format.
Click to expand...
Click to collapse
Finally working adb drivers for ICS/JB in Windows!
This is an adb driver for Windows. LG's adb driver wasn't working for Android 4.0+ ROMs before they (finally) released their ICS update.
I modded Googles adb usb driver to work with the LG 2x (P990/P999).
Additionally this driver does work in CWM6 - especially useful as there are still some recoveries which aren't able to mount usb storage - with adb you can workaround that and adb push files to the /sdcard.
Installation instructions:
Download and extract this zip: http://goo.im/devs/tonyp/modded_adb_driver (use the newest version)
Win8 users only: You need to disable the driver signature enforcement. Follow the instructions in the second post.
Open the device manager
Rightclick LG-P990 (or similiar) and choose "Update Driver Software..."
Choose to "Browse my computer for driver software"
Click on Browse and navigate to the extraction folder
Hit next and choose the second option "Install this driver software anyway"
Done!
Troubleshooting:
If no driver gets found at step 7 your phone probably got a different Hardware ID.
I added all Hardware IDs for the LG 2x I am aware of, but there might be additional ones.
Please post your ID in this thread and I will release a new version of the driver for you
This screenshot shows which information I need: http://www.screencast.com/t/Z41IUcpq2
Win8 instructions:
To install an unsigned driver you need to disabe driver signature enforcement (sorry, I can't afford the 2000$ to buy a signing licence )
You need to do an advanced reboot.
Easiest way: Hit Win+R, type in the following command and hit enter:
Code:
shutdown -o -r -t 0
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart
After the restart choose the option "7" - ‘Disable driver signature enforcement‘
Now install the driver as written in the OP. After your next reboot the enforcement gets enabled again.
Oups, I just wanted to reserve one post, well as I have this post now anyways I will use it to link to the following comic:
http://www.joke-portal.com/cell_phone_users_iphone-android-blackberry.jpg
Great !!!!!!! Big step for us, many thanks!
I don't use ICS, but the comic is fantastic ahahahah!!
Inviato dal mio LG-P990 con Tapatalk 2
Is there a tl;Dr version of the modding you did? I'm interested in these kind of things.
Sent from my LG-P990 using xda app-developers app
awesome work, finally got full adb access to my phone
Nice work tonyp! This is really useful!
Sent from my LG-P990 using Tapatalk 2
Thanks a bunch. Been a waiting a while for these. Good work!
Sent from my LG-P990 using xda app-developers app
Good work
Sent from latest Django Manouche with latest Spica Kernel
Thanks for your work.
I just need it.
Yet, it does not update the driver successfully.
ykin said:
Yet, it does not update the driver successfully.
Click to expand...
Click to collapse
What do you mean?
tonyp said:
What do you mean?
Click to expand...
Click to collapse
I mean with the debug on, the device manager shows P990 with a warning sign.
But it didn't allow to update with your driver.
Thanks for your concern. :highfive:
ykin said:
I mean with the debug on, the device manager shows P990 with a warning sign.
But it didn't allow to update with your driver.
Thanks for your concern. :highfive:
Click to expand...
Click to collapse
Hm okay that's odd, because it seems to work for most people.
Please try again to follow the instructions precisely.
If this doesn't work you can try these alternative driver test version: testversion
If this one doesn't work for you as well I need the Hardware ID of your P990. Double click P990 in the device manager, go to Details and select Hardware ID.
Looks like this: http://www.screencast.com/t/Z41IUcpq2
tonyp said:
Hm okay that's odd, because it seems to work for most people.
Please try again to follow the instructions precisely.
If this doesn't work you can try these alternative driver test version: testversion
If this one doesn't work for you as well I need the Hardware ID of your P990. Double click P990 in the device manager, go to Details and select Hardware ID.
Looks like this: http://www.screencast.com/t/Z41IUcpq2
Click to expand...
Click to collapse
It dosen't work for me either! Mine is a LGP990h and i need to use it as a modem, but because of the driver's i cant, already tried your's but it's a no go.
I'll attach my hardware ID, Thanks.
não-soi-jo said:
It dosen't work for me either! Mine is a LGP990h and i need to use it as a modem, but because of the driver's i cant, already tried your's but it's a no go.
I'll attach my hardware ID, Thanks.
Click to expand...
Click to collapse
I included your hardware ID in the driver: https://dl.dropbox.com/u/2478159/android/testing_P99x_adb_usb_driver.zip
Please give some feedback if you're able to install it now.
But: This driver enables adb only, not the usb modem.
Thanks, will try it. I thougt it would enable thearing to. Thanks anyway.
tonyp said:
Hm okay that's odd, because it seems to work for most people.
Please try again to follow the instructions precisely.
If this doesn't work you can try these alternative driver test version: testversion
If this one doesn't work for you as well I need the Hardware ID of your P990. Double click P990 in the device manager, go to Details and select Hardware ID.
Looks like this: http://www.screencast.com/t/Z41IUcpq2
Click to expand...
Click to collapse
Thanks for your help. It's working now!!
I have set the ID to USB\VID_18D1&PID_6866.
New version up. No need to upgrade if the old version works for you, there are no changes to the driver, I just made the driver compatible to two new Hardware ID's (P990h and I think P990 white).
Hi Tonyp,
It also doesn't work for me.
It seems like the driver installs correctly (no exclamation mark in device manager anymore), but I get:
Code:
c:\Program Files (x86)\tools\Android Injector>adb devices
List of devices attached
4360655703648044 offline
c:\Program Files (x86)\tools\Android Injector>adb shell
error: device offline
This is my device ID:
Related
BACKTOP v0.00001
Click to expand...
Click to collapse
Alright, so this is a guide to finally get the backtrack 5 software running inside of webtop. It uses chroot and xterm to allow full access to the software contained within the backtrack 5 arm image.
Prerequisites:
CWM Installed:
For all version: http://forum.xda-developers.com/showthread.php?t=1138541
WebTopMOD installed:
For 2.3.4 go here: http://forum.xda-developers.com/showthread.php?t=1169457
For 1.8.3 go here: http://forum.xda-developers.com/showthread.php?t=1093790
You do not need to download the Debian disk image. Will we be using the backtrack disk image instead.
BusyBox Installed in /system/bin:
Downloaded "BusyBox Installer" from the app store.
BE SURE TO INSTALL IN /SYSTEM/BIN!
Click to expand...
Click to collapse
The Goods:
BackTop.zip:
Download and un-zip the attached files into /sdcard/bt
BackTop.zip
BackTrack 5 ARM Image:
PART 1 : Download Link : http://bit.ly/p1BT5
PART 2 : Download Link : http://bit.ly/BT5p2
PART 3 : Download Link : http://bit.ly/BT5p3
These download links are from the xperia backtrack project and where I took inspiration to get it working in webtop. After using 7z to unarchive just place bt.img in the /sdcard/bt folder. The archives other contents can be safely ignored.
Click to expand...
Click to collapse
What you should have by now:
WebTOPMOD for Atrix.
BusyBox Installed in /system/bin.
Downloaded scripts placed in the /sdcard/bt folder.
Downloaded bt.img placed in the /sdcard/bt folder.
Click to expand...
Click to collapse
Give it a go:
Step 0: Connect the phone to display/lapdock. Run webtop and wait for it to boot.
Step 1: Open LXTerminal from the dock and type "cd /sdcard/bt"
Step 2: To run BackTop type "sudo bash backtop"
You should be presented with a white xterm screen. You can now use all the utilities built into backtrack 5 with ease. You can even run the gnome desktop environment! (More on that bellow)
Click to expand...
Click to collapse
Running Gnome:
You first need to kill off all the webtop crap do this by typing the following in xterm.
"ps ax|grep awn|awk '{print $1}'|xargs kill"
"ps ax|grep panel|awk '{print $1}'|xargs kill"
Then start gnome by typing "gnome-session" in xterm.
Click to expand...
Click to collapse
Accessing sdcards:
You'll need to make two directories inside of backtrack /sdcard and /sdcard-ext to do this type:
"sudo mkdir /sdcard"
"sudo mkdir /sdcard-etc"
Once you've done this simply reboot your phone and restart BackTop.
Click to expand...
Click to collapse
Known issues:
ettercap causes network connectivity inside of webtop to fail.
If something does go terribly wrong you can always force quit backtop with the following command:
"sudo bash /sdcard/bt/forcekillbt"
Click to expand...
Click to collapse
Cool stuff, I'll definitely check this out. Moved to development.
mate I don't have webtop but as a network engineer I'm giving this a big thumbs up, super cool to have a pen testing suite in your phone!!!
reserved #10Chars
It might just be me but do your links work? Specifically the http://bit/ly ....etc. thanks
Sent from my MB860 using XDA App
edit: had a smart attck and everything is tip top...well done sir...thx!!
that is the most metal thing ever
I'd prefer it actually dual boot on my phone for hac..I mean testing on the go xD
What will this one do that the others don't?
Cheers
pederb said:
What will this one do that the others don't?
Cheers
Click to expand...
Click to collapse
If you don't know what BackTrack is then you don't need it.
pederb said:
What will this one do that the others don't?
Cheers
Click to expand...
Click to collapse
its a pen testing Linux suit. its essentially Linux loaded up with hacking tools meant for testing networks to prevent hacking or "penetration". hack your own network. discover the vulnerabilities. and patch them. - to put it simply
This is amazing. Thanks.
7z issue with the bt.7z
Hum... I might be doing something wrong but I am not able to uncompress the 3 volumes posted in the links... I was able to download them all but the only one who actually I can uncompress is the first one and it generate a file bt.7z that I am also unable to uncompress... I am getting the following msg when I try to 7unzip them:
"cannot open file 'x:\xx\xx\bt.7z.002' as archive"
Should I join them all into one then use 7zip?
Forget it I just found it out by myself... is using a program to join them all into one then Unzip it.
My dream come true .............. i assume that we can run kismet and metasploit framework ?!
What kernel and rom were you able to make this run well with as i am having really bad reboots after i undock the phone from the lapdock as i am running faux123 kernel and cherry crust v3.
webtop when connected to hdmi not doing anything...
I was trying to use this backtrack distro on my AT&T Atrix and I must admit that I am a kind of noob on this ... I wasn't seeing big advantage until now that we have bt to use instead of the stock version...
I have no Lapdock so I am using Ronaldo_9 CWM version to run Webtop on HDMI in my GB 2.3.4 ( 4.5.91 from Kenneth Penn ). It was working til I followed these instructions ...
Well a little bit of what I did:
1- Downloaded the WebTopMOD from Joe Ferreira v2 to install with CWM.
2- Got also BusyBox installed through the BusyBox Installer over my /system/bin
3- Downloaed (even knowing it's not needed) the Debian disk from Joe Ferreira link (to install webtopmod).
4- Downloaded the BlackTrack 5 image from the links on the first post
5- Downloaded the BackTop.zip from the first post
6- Created the /sdcard/bt folder and put only the bt.img and forcekillbt and backtop files from Backtop.zip file onto it...
7- Plugged in my HDMI cable over my tv (yes I have no lapdock)
8- The Webtop option pop's up and when I selected it.....
Nothing happened... not even an error msg or stuff... the only thing still working is EC... but webtop none.... Does anyone of you have any clue or hint of what can I do about it?
EDIT: Got it working... it was because of the broken V2 WebtopMOD so I flashed the V1 and everything went fine.... Thank you all for not helping it made me a better researcher
I think I just wet myself I've been waiting for someone to come up with this since they started the ARM archticture and ported it to the XOOM tablet
Sent from my MB860 using XDA Premium App
The built in wifi doesn't support packet injection does it?
baumerman said:
The built in wifi doesn't support packet injection does it?
Click to expand...
Click to collapse
It doesnt....
Sent from my MB860 using XDA App
BCM4329 supports Promiscuous Mode and Multiple Monitor mode.
It supports Packet Injection, too.
The WiFi module needs to be modified for enabling these things... I'm currently working on GenTop, but after finishing that work I can take a look at it and see if I'm skilled enough to enable it on the driver.
kholk said:
BCM4329 supports Promiscuous Mode and Multiple Monitor mode.
It supports Packet Injection, too.
The WiFi module needs to be modified for enabling these things... I'm currently working on GenTop, but after finishing that work I can take a look at it and see if I'm skilled enough to enable it on the driver.
Click to expand...
Click to collapse
That would be awesome... just amazing how u dealing with a lot of stuffs simultaneously ....... tyvm for visiting this thread its almost dead...
Doing a simple (means not a complex one) research at Google it seens that there's no much of Monitor mode for android cell phones so far... not sure why if nobody cares or if it's not possible... but u got skill enough to give the last word
Hope to hear something soon...
I wish there was more development for this, and +1 for packet injection
gzrecoil said:
I wish there was more development for this, and +1 for packet injection
Click to expand...
Click to collapse
There is monitor mode for iPhone and itouch... not sure the reason why not for android :-(
Sent from my MB860 using XDA App
Ok after some hours of trial and error Im able to read and write to my one with qpst. I'll share my setup.
I'm on windows 8 64bit
I've attached the build of qpst I used as well as the driver.
If your on windows 8 or 7 you will have to disable the signed driver check
open command prompt by running as an administrator, then issue this command
bcdedit /set {globalsettings} advancedoptions true
reboot.
Once windows restarts choose option 7 to disable driver check.
Connect your phone with the usb cable and enter diag mode by press ##3424#
Two drivers should fail to load
Htc diag
Htc diag9k
Right click on the htc diag9k driver and click on "update driver software"
select "browse my computer for driver software"
Then "let me pick from a list of device drivers on my computer"
click have disk and navigate to where you extracted the driver files
and choose Qualcomm HS-USB Android Diag 9018
Click next till it is installed and you should be ready to open qpst
you will need your msl/spc code but there is a thread on a easy way to retrieve that.
The archives you attached are corrupt.
ProfessorAnomaly said:
The archives you attached are corrupt.
Click to expand...
Click to collapse
I Think actually it was my drop box, try them now
wranglerray said:
I Think actually it was my drop box, try them now
Click to expand...
Click to collapse
still not working,. corrupt
jcwxguy said:
still not working,. corrupt
Click to expand...
Click to collapse
It worked for me.
They're corrupt. I tried downloading multiple times, using different browsers on my PC as well as using different software to open the archives.
jkt97401 said:
They're corrupt. I tried downloading multiple times, using different browsers on my PC as well as using different software to open the archives.
Click to expand...
Click to collapse
I had no problem d/l and getting this installed. I am not doubting you, just odd that it works for me ok.
Corrupt for me as well
Sent from my HTCONE using XDA Premium HD app
Why not just use cdmadevterm?
What about CDMA workshop and qxdm?
Sent from my SGH-T889 using xda premium
Useful info
Just to let everyone know...
I just loaded the normal HTC Diag drivers I have been using for years for the diag9k. Was able to access it in QPST , CDMA WS (paid version) , and DFS . (The regular htc diag wouldn't respond to any of the commands sent to it with using the normal drivers, I will try with the ones posted but I am thinking that we really should only need to work with the 9k). Same thing applies with any htc phone of recent years, if you want acess to NV folder, create a folder called "open sesame door" in the main directory while using efs explorer in qpst or in DFS read EFS2 and create the folder. Reboot the phone and the folder will be accessible. QPST is the better option since when in DFS it doesn't show some of the key files you need to work with *cough cough*. Same HTC supercode works and cdma WS is able to find the SPC just fine. Another fun fact for people to know. The one does function for calls text and internet without the sim card , just no lte , which for some this might be helpful ( >=) ). Always some fun menus to change settings under ##3282# as well. Hope this helps some people out!
I would love to get QPST working with my Sprint HTC One. So far everything I have tried hasn't worked.
The linked drivers are corrupt for me as well (tried WinRAR and 7-Zip). Any new links possibly?
The attached files are actually HTML. I just changed the extension to "htm" and loaded it in a browser. It opens the Dropbox download page.
I'm working on the driver signing issue now.
Richard
My QPST screen
I now have the attached drivers installed. I still get exactly what I was getting with several other HTC diag drivers.
It looks like something is found, but the phone isn't recognized.
Any thoughts?
Richard
Hello i cant install the drivers since it says that the drivers are not digital signed, can some one tellme how can i install them? i already tyed the comand prompt, and other ways, but allways says that theres an error installing them... Tahnx
Thanks!
wranglerray said:
Right click on the htc diag9k driver and click on "update driver software"
select "browse my computer for driver software"
Then "let me pick from a list of device drivers on my computer"
click have disk and navigate to where you extracted the driver files
and choose Qualcomm HS-USB Android Diag 9018
Click next till it is installed and you should be ready to open qpst
you will need your msl/spc code but there is a thread on a easy way to retrieve that.
Click to expand...
Click to collapse
Thank you...
I tried the instruction exactly as posted but could not get the Diag9k drivers to work. The drivers do get installed but there is a yellow triangle showing and an error massage comes up stating that the drivers are not compatible with the device. Can somebody let me know how to install the drivers correctly?
championwaqas said:
I tried the instruction exactly as posted but could not get the Diag9k drivers to work. The drivers do get installed but there is a yellow triangle showing and an error massage comes up stating that the drivers are not compatible with the device. Can somebody let me know how to install the drivers correctly?
Click to expand...
Click to collapse
Try this
http://www.cricketusers.com/showthread.php?t=85426
Sent from my HTCONE using Tapatalk 4 Beta
I made my own driver and got full qpst... I can configure my cell and note it's working...
Sent from my HTCONE using xda premium
cciemd said:
I now have the attached drivers installed. I still get exactly what I was getting with several other HTC diag drivers.
It looks like something is found, but the phone isn't recognized.
Any thoughts?
Richard
Click to expand...
Click to collapse
Upgrade your qpst versions. Work for me
Sent from my HTCONE using xda premium
Thx its works
Yes Thx u very much now its work on my computer Macbook pro 15 windows 8 with QPST ,
cciemd said:
I would love to get QPST working with my Sprint HTC One. So far everything I have tried hasn't worked.
The linked drivers are corrupt for me as well (tried WinRAR and 7-Zip). Any new links possibly?
The attached files are actually HTML. I just changed the extension to "htm" and loaded it in a browser. It opens the Dropbox download page.
I'm working on the driver signing issue now.
Richard
Click to expand...
Click to collapse
I hated to always have a whole android library installed so here is a protable ADB version. (only 10mb including the drivers)
Steps:
1. Download (http://d-h.st/k70)
2. Unzip.
3. Install driver (Driver version from: 30-01-2014)
4. CMD to the folder and run ADB
Driver problems?
Follow this topic:
http://forum.xda-developers.com/showthread.php?t=2513339 (thanks 1wayjonny)
Thanks for this! It's cool that the kit you linked supports the big three platforms as well.
You mentioned going to the thread you linked at the bottom of your post if you need drivers, but there appear to be drivers bundled with it.
Melamunna said:
Thanks for this! It's cool that the kit you linked supports the big three platforms as well.
You mentioned going to the thread you linked at the bottom of your post if you need drivers, but there appear to be drivers bundled with it.
Click to expand...
Click to collapse
Yea ignor those just some test stuff I was working on (also don't try the boot.img)
gkillerx said:
Yea ignor those just some test stuff I was working on (also don't try the boot.img)
Click to expand...
Click to collapse
Do you want a ZIP without the boot.img and drivers?
Melamunna said:
Do you want a ZIP without the boot.img and drivers?
Click to expand...
Click to collapse
No need to. I will make an all in one portable package for the nexus 5 give me a sec.
Updated first post.
Thanks mods for placing this is the right section
Sent from my Nexus 5 using Tapatalk
Can I use this tool with any Android version (eg 4.4, 5.1)? With any ROM (Stock, CyanogenMod, Carbon etc…)?
Drivers apart, can I use this tool with any devices?
Nice one mate, thank you!
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.