Hello I installed a new FW on my Ouya and it killed CWM recovery. Right now I'm stuck at the device manager and it list my Ouya as other device and fastboot is under that. I tried installing the drivers from OneClickOuyaRecovery.zip, but it doesn't work. What am I doing wrong?
Install the adb sdk then your going to want to install the Google drivers and add a line of code to the file under nexus to make It work with the ouya. Your going to have to Google it or maybe some one can file you in better on it. I'm at work and don't have access to a computer to give you a 100% detail on how to do it. Like I said just Google it that's how I found out how to make it work.
Sent from my SCH-R970 using Tapatalk
samt3 said:
Install the adb sdk then your going to want to install the Google drivers and add a line of code to the file under nexus to make It work with the ouya. Your going to have to Google it or maybe some one can file you in better on it. I'm at work and don't have access to a computer to give you a 100% detail on how to do it. Like I said just Google it that's how I found out how to make it work.
Sent from my SCH-R970 using Tapatalk
Click to expand...
Click to collapse
Yep I had the adb drivers installed, but not the fastboot drivers. I found them here: http://forum.xda-developers.com/showthread.php?t=1582554. CWM recovery installed and works fine.
Thanks
Related
I have always been able to get ADB working over USB in Clockwork Recovery. Recently I tried out TWRP as an alternative, and I really like it, but I couldn't get ADB to work. Is that just not available in TWRP, or are there other drivers I need to install? Or is there an option I need to enable?
Sent from my Galaxy Nexus using Tapatalk 2
cmstlist said:
I have always been able to get ADB working over USB in Clockwork Recovery. Recently I tried out TWRP as an alternative, and I really like it, but I couldn't get ADB to work. Is that just not available in TWRP, or are there other drivers I need to install? Or is there an option I need to enable?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
It should work... What driver are you using?
Mount /data?
Make sure your pushing to /data/media?
Is adb not working period like adb devices returns nothing or it won't push?
Sent from my Galaxy Nexus
Also could you do adb devices? This will show if the adb detects your phone or not. If you see a serial number, then the adb recognizes your phone and you're doing something wrong ( such as wrong command or won't directory)
Swyped on my Galaxy Nexus running AOKP with Franco Kernel
ADB devices works when booted into the OS, and works from CWM. I get nothing listed under ADB devices when in TWRP.
I'm using whatever drivers I installed when I first bought my GNex.
It's TWRP v 2.3.1.0, installed from the Goo Manager app.
EDIT: Odd, I unplugged/replugged the phone and now it does show up in recovery. Maybe it doesn't click in if I reboot with the phone attached.
Let me further amend... it does not appear on adb devices until I open up Windows Device Manager and tell it to scan for hardware changes. Then after about a minute the phone appears in adb devices.
With CWM it appears instantly in adb devices, no delay.
well, post your issue in TWRP [email protected] section
bk201doesntexist said:
well, post your issue in TWRP [email protected] section
Click to expand...
Click to collapse
Where is that thread? I'm also facing the same issue in my ZTE V970M...
Nevermind, sorry for the necroposting. I solved it by installing ZTE Composite ADB Device in the C:\Program Files\ZTE <whatever>\Driver\amd64 folder. Using Win8 x64 btw.
Are there any real benefits for rooting the Ouya?
I've looked endlessly for the google driver so that the Ouya Toolbox can recognize my console and I can't find it anywhere.
Can anybody post the file so I can manually add it? When I download the SDK from Android, there's nothing like the folders where the driver should be... and its nowhere to be found.
Theoretically once I have the driver I should be able to root it, right?
Thanks!
robguerra said:
Are there any real benefits for rooting the Ouya?
I've looked endlessly for the google driver so that the Ouya Toolbox can recognize my console and I can't find it anywhere.
Can anybody post the file so I can manually add it? When I download the SDK from Android, there's nothing like the folders where the driver should be... and its nowhere to be found.
Theoretically once I have the driver I should be able to root it, right?
Thanks!
Click to expand...
Click to collapse
Shure there are, like being able to
install Google Play Store
install Custom Roms
install CWM recovery
backup your system
use CIFS to mount network storage (if your kernel supports it)
use USB Drives for additional app storage
etc.
Basically, without root the Ouya would be rather useless for me.
Regarding the driver: I use adb via Linux, but if I'm not mistaken, you have to download the drivers from within the SDK.
The tuts in the dev section spell out what needs to be installed within the SDK. You can also use Samsung adb drivers from KIES.
Sent from my GT-P3113 using Tapatalk 4 Beta
Just do the one-click method from here:
http://forum.xda-developers.com/showthread.php?t=2295645
Then install the StockPlus ROM that includes Google Play, etc from here:
http://forum.xda-developers.com/showthread.php?t=2347214
Very easy to do so, no need to actually set up the SDK. Just need a USB keyboard and about 5 minutes. Only part that requires any type of work is after installing CWM is pushing the ROM to /sdcard/ on the Ouya, then adb reboot bootloader and do the rest. Very easy. In Windows 8 64-bit you'll need to disable driver signature enforcement, just Google it only take a minute or two.
Ok, this isn't my first rodeo as I've owned many android devices including the old nexus 7. I'm trying to unlock and root this but I can't install the drivers. I tried the device manager method and when I search it can't find anything and I tried a website to manually do it by downloading a zip and choosing it to no avail. Any one have the link to the drivers as that website may not of been accurate or anyone have any other suggestions?
You need to unzip it first.
Username invalid said:
You need to unzip it first.
Click to expand...
Click to collapse
Yes I did that and it only had two folders that showed up while browsing in the update drivers part in device manager. One was AMD86 and the other was i3 something and neither of those matched the picture in the steps but I used the link given within the same tutorial.
http://developer.android.com/sdk/win-usb.html
Username invalid said:
http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
Ok I still cannot install the drivers. When I downloaded the file provided in that link, there are no driver options at all. There are only two folders in which I described in my previous post and neither have drivers in them. I'm no noob and have done this plenty of times, I even tried to adb reboot bootloader and it says device not found and yes USB debugging is on so I'm assuming I can't do anything until I some how install the drivers.
Which website guide are you looking at?
Username invalid said:
Which website guide are you looking at?
Click to expand...
Click to collapse
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
C-4Nati said:
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
Click to expand...
Click to collapse
If nothing else works, you might consider partitioning your hard drive and installing a secondary OS. Both Windows 8.1 and Ubuntu worked for me no problem.
Code:
sudo apt-get install android-tools-adb
sudo apt-get install android-tools-fastboot
adb reboot bootloader
fastboot oem unlock
fastboot reboot-bootloader
cd Downloads
fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
adb push update-supersu-v1.51.zip /sdcard/Downloads
C-4Nati said:
The one on the site. Ok I installed SDK manager and I checked google usb drivers in it and it installed it, but when I do the adb commands it still says device not found -.-
Click to expand...
Click to collapse
Ok I installed the drivers correctly, I figured it out. Now when I try the adb commands it says device offline when it's clearly not lol...
I've got everything working now and unlocked and rooted. I appreciate all the help you have offered to me. I do not remember it being this difficult with the original Nexus 7 lol.
C-4Nati said:
Ok I installed the drivers correctly, I figured it out. Now when I try the adb commands it says device offline when it's clearly not lol...
Click to expand...
Click to collapse
Fastboot is all you need to root your device.
C-4Nati said:
I've got everything working now and unlocked and rooted. I appreciate all the help you have offered to me. I do not remember it being this difficult with the original Nexus 7 lol.
Click to expand...
Click to collapse
I'm having a similar problem with drivers, why don't you post how you solved it? I am trying on 2 different windows 7 machines. google drivers don't load, asus drivers don't load. Device manager just says "windows could not find driver software for your device."
---------- Post added at 08:15 PM ---------- Previous post was at 08:13 PM ----------
I figured it out, have to turn MTP on, then install drivers - then you can turn MTP back off if you want.
Ok, I installed TWRP via freegee. I then proceeded to wipe my ROM, but realized too late i did not have the ROM i wanted on the phone. Any ideas on how to put a rom on it?
jaredtheoverlord said:
Ok, I installed TWRP via freegee. I then proceeded to wipe my ROM, but realized too late i did not have the ROM i wanted on the phone. Any ideas on how to put a rom on it?
Click to expand...
Click to collapse
Go in to TWRP> Advanced> adb sideload, now (must have ADB installed and phone connected to computer) have the desired file to flash on your computers desktop and now hold the shift key and right mouse click> open command window here. Then in this command window type adb sideload rom.zip (whatever the actual name of the zip file is included .zip at the end)
TWRP install ROM from SD slot. Hell, it can even be installed via a mounted USB OTG stick. Did you try putting you ROM onn an SD card and try it?
uppon2 said:
Go in to TWRP> Advanced> adb sideload, now (must have ADB installed and phone connected to computer) have the desired file to flash on your computers desktop and now hold the shift key and right mouse click> open command window here. Then in this command window type adb sideload rom.zip (whatever the actual name of the zip file is included .zip at the end)
Click to expand...
Click to collapse
I followed your instructions however i am getting a device not found error
zerogun said:
TWRP install ROM from SD slot. Hell, it can even be installed via a mounted USB OTG stick. Did you try putting you ROM onn an SD card and try it?
Click to expand...
Click to collapse
I tried by an SD card and it was not detected
jaredtheoverlord said:
I followed your instructions however i am getting a device not found error
Click to expand...
Click to collapse
Make sure drivers for your phone is installed. And do yu already have ADB installed in your pc?
Sent from my LG-E980 using Tapatalk
babymatteo said:
Make sure drivers for your phone is installed. And do yu already have ADB installed in your pc?
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
Im not sure i have the correct drivers, do you know where i can find them?
jaredtheoverlord said:
Im not sure i have the correct drivers, do you know where i can find them?
Click to expand...
Click to collapse
Google search my friend.
Sent from my LG-E980 using Tapatalk
babymatteo said:
Google search my friend.
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
I have the one from LG's site installed, is that the correct one?
jaredtheoverlord said:
I have the one from LG's site installed, is that the correct one?
Click to expand...
Click to collapse
Uninstall/reinstall them. Make sure you have ADB installed correctly too (google/youtube for this). Change USB ports on your computer perhaps? - If this is all done correectly there will be no reason it will fail unless there is a hardware issue
uppon2 said:
Uninstall/reinstall them. Make sure you have ADB installed correctly too (google/youtube for this). Change USB ports on your computer perhaps? - If this is all done correectly there will be no reason it will fail unless there is a hardware issue
Click to expand...
Click to collapse
Ok, I will after school, I will also use my other PC to see if that works
jaredtheoverlord said:
Ok, I will after school, I will also use my other PC to see if that works
Click to expand...
Click to collapse
Let me know if you are having any more problems and I will help you one on one to install ADB correctly and get your phone going for you mate. I am in Australia so our timezones might be a bit off but let me know
I have a second gen kindle fire (rooted) and looked and looked all over and have not seen any way to use custom launchers on my kindle fire. It downloads and installs but does not show up in the carousel or application list. i go into lucky patcher and it cannot open the launcher. Please give reason and or fix
illusion_insanity said:
I have a second gen kindle fire (rooted) and looked and looked all over and have not seen any way to use custom launchers on my kindle fire. It downloads and installs but does not show up in the carousel or application list. i go into lucky patcher and it cannot open the launcher. Please give reason and or fix
Click to expand...
Click to collapse
Try rebooting. It could also be intentional behavior on Amazon's side (they won't let you change the default launcher, and they might prevent you from even opening another one).
Sent from my Amazon Jem using XDA Labs
thanks
i am no a pro at this but i think someone said its because it has a locked bootloader.
illusion_insanity said:
i am no a pro at this but i think someone said its because it has a locked bootloader.
Click to expand...
Click to collapse
The issue isn't caused by a locked bootloader; however, unlocking or replacing the bootloader will allow you to use a custom ROM and sidestep the stock OS's restrictions.
Thanks
monster1612 said:
The issue isn't caused by a locked bootloader; however, unlocking or replacing the bootloader will allow you to use a custom ROM and sidestep the stock OS's restrictions.
Click to expand...
Click to collapse
I guess I can trial and error my way until it works! do you think I should just get cyanogem mod on it if I can't get a launcher?
illusion_insanity said:
I guess I can trial and error my way until it works! do you think I should just get cyanogem mod on it if I can't get a launcher?
Click to expand...
Click to collapse
Yep - it'd be more up to date than Amazon's stock OS, too.
Sent from my Amazon Jem using XDA Labs
monster1612 said:
Yep - it'd be more up to date than Amazon's stock OS, too.
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
the thing is, I don't have the adb drivers to use kindle fire utility
illusion_insanity said:
the thing is, I don't have the adb drivers to use kindle fire utility
Click to expand...
Click to collapse
What OS are you using on your PC? If you're running Linux (Ubuntu, etc.), no drivers are needed.
windows
monster1612 said:
What OS are you using on your PC? If you're running Linux (Ubuntu, etc.), no drivers are needed.
Click to expand...
Click to collapse
I am using windows seven. but it wants me to have android sdk in the majority of the tutorials I've read
illusion_insanity said:
I am using windows seven. but it wants me to have android sdk in the majority of the tutorials I've read
Click to expand...
Click to collapse
The tutorials recommend you install the Android SDK, but unless you're planning on doing Android app development, most of the SDK will be useless. Instead of using the SDK (which is quite bulky), I'd recommend that you run the 15 second ADB installer, which can be downloaded here. Run the program as administrator, and when you're asked the questions, answer Yes/Y for the "install ADB and fastboot" and "install ADB system wide" questions, and No/N to the "Install device drivers" question. The reason we're not installing the drivers bundled with the installer is because the drivers are for Google devices, which will clearly not work with the Kindle.
Because of this, we're going to install the Kindle drivers separately. Go ahead and download the zip file in this thread, which contains installers for the Kindle drivers. Unzip the folder, run one of the executables as administrator, and install the drivers as prompted. You may get errors about installing unsigned drivers - continue anyway. Once the drivers successfully install, reboot your machine. Once you're rebooted, plug in your kindle (make sure it's booted into either recovery or a ROM). (NOTE: If you're booted into a ROM, you may get a prompt asking if you want to allow USB debugging. If you get this message, check the "Always allow from this computer" checkbox, and then OK.) Open a command prompt window and type adb devices. Below "list of devices attached", you should get a random string back (this is your device's ID) and either "unauthorized", "offline", or "device" next to it. If you don't see any text below "List of devices attached", then check to make sure ADB is enabled on your kindle (which it probably is if you rooted it ).
AWESOME
Have see it tried it yet but I will I gave ed up with sdk I have crap internet so it takes forever to download. I needed this thanks alot