its pretty early in the morning and all i want to do is sleep, so i got to apologize for possible typos and lazy writing, and whats even worse is that im a complete noob on the android platform, so please bear with me. (hi, im the new guy btw)
anyways, i fu'd my "su" up by resetting after rooting and now i cant sideload the ota in recovery mode to fix it.
what i do:
get ouya into recovery (adb reboot recovery) and select "something something from adb"
(sorry, its really, REALLY early and i ran out of coffee)
the screen then gives me the message:
Now send the package you want to apply to the device with "adb sideload <filename>"...
and thats the point where im stuck, after typing "adb sideload RC-OUYA-1.0.346-r1_ota.zip" it just tells me: error: device not found.
i also tried "adb install RC-OUYA-1.0.346-r1_ota.zip" but that just gave me the same error with the message "- waiting for device -" below.
also adb doesnt recognize the ouya in recovery mode (adb devices gives me an empty list) but DOES recognize the console out of recovery.
i can also still boot it up and play with the settings, the only issue is that sometimes wifi just randomly refuses to work (and i dont have any games installed so i cant test that)
its not really important but,
what i did:
i sucessfully finished the [how to] adb sideloading superuser-access tutorial by ty collum (not the wireless part)
and then i tried booting CWM (the one click batch thing) which gave me the "OUYA!" screen (just like in recovery mode) so i made a factory reset, after which i couldnt access su anymore. (which again is why i want to sideload the ota, to start over.)
thats all i can think of for now, if someone needs more infos just ask, apologies again for being a little inconvenient, but im really tired.
sincerely smokey.
EDIT:
nobody has even the slightest clue what could cause this? drivers, missing librarys, a bug in the sdk, nothing?
just reinstalled windows 7 ultimate x64 (had to do it anyway) and going to retry the procedure now, reporting back once im done.
UPDATE
solved it by trial & error. what happened:
apparently my (any?) ouya changes its hardware id after going into recovery, so i had to reinstall the driver IN recovery mode:
its basically the driver installation procedure
(google "setup instructions for the ouya odk" for a text or "ouya on windows driver setup" for a video tutorial)
with a slight change, instead of pasting:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
into the android_winusb.inf open your hardware monitor and check your ouya's hardware id
(right click on the device->properties->details->and select hardware id's from the dropdown menu,
you need the one WITHOUT "REV_xxxx" in it)
and replace your id with the one in the "%CompositeAdbInterface%" line above, in my excample it now looks like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, [B]USB\VID_18D1&PID_D001[/B]
EDIT
at this point you can simply continue the driver installation tutorial
Click to expand...
Click to collapse
after that proceed to sideload the ota via "adb sideload *filename*.zip"
also it now shows up in the "adb devices" list while in recovery mode (my ouya never showed up in recovery before)
greetings smokey.
THANKS!!!
iAmSmokey said:
UPDATE
solved it by trial & error. what happened:
apparently my (any?) ouya changes its hardware id after going into recovery, so i had to reinstall the driver IN recovery mode:
its basically the driver installation procedure
(google "setup instructions for the ouya odk" for a text or "ouya on windows driver setup" for a video tutorial)
with a slight change, instead of pasting:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
into the android_winusb.inf open your hardware monitor and check your ouya's hardware id
(right click on the device->properties->details->and select hardware id's from the dropdown menu,
you need the one WITHOUT "REV_xxxx" in it)
and replace your id with the one in the "%CompositeAdbInterface%" line above, in my excample it now looks like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, [B]USB\VID_18D1&PID_D001[/B]
after that proceed to sideload the ota via "adb sideload *filename*.zip"
also it now shows up in the "adb devices" list while in recovery mode (my ouya never showed up in recovery before)
greetings smokey.
Click to expand...
Click to collapse
you are a legend, i was having the same issue with x64, i just did a system restore to back up right before I started all this jazz. through hours of researching, regarding how to reset my drivers from the MTP USB device, to click ALT+Sysrq+i for a solid half hour. this post with the the slight alter in code was the final touch to being able to sideload. my OUYA is now back up and running! THANKS!
You can also append the line, you don't have to replace it.
Like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
%CompositeAdbInterface% = USB_Install, [B]USB\VID_18D1&PID_D001
[/B]
Btw thanks mate!
Related
Just hooked this baby up. Amazon, of course, doesn't provide any information on USB drivers or on how to enable debugging on the device. Probably one of their attempts at "security".
Anyway, looking for two things:
1. Any leads on drivers for windows. I could also do this on a Mac
2. How to enable debug mode so that I can actually test my damn apps on the device.
Everyone keeps talking about how they suspect this is running on cheapened-up BB Playbook hardware... not sure that would help at all...
breon said:
Found it. It's pretty easy. http://blog.actlocalmedia.com/2011/11/developing-on-kindle-fire.html
Click to expand...
Click to collapse
keyesdav, this should help. Thought I'd cross-post (cross-quote?) it over here in case you didn't see / haven't found it yet.
I was able to use the google adb driver on win7 x64, but you have to add the device id to the ini file.
Edit %androidsdkdir%\google-usb_driver\android_winusb.inf
Try adding the following lines under [Google.NTx86] AND [Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Still unable to get Kindle Fire to attach to Win 7 x64
I have a Lenovo W520 laptop. I've made these changes, however the Kindle Fire still comes up unrecognized in the Device Manager.
adb devices shows nothing
repeated adb kill-server, adb start-server no change
Help!
BTW, my "google_usb_driver" directory is in C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver.
Did they move it recently?
Did you go to Device Manager on your PC and then select the Kindle 'Unknown Device' and update the driver by selecting the Inf file you had edited? After updating the driver the system will then show the ADB connection. This is the same process to go through when doing the Root.
That worked!! Thanks!
(I didn't have to do this when I rooted my Galaxy Tab. Samsung provided a driver.)
So I have my Kindle Fire rooted, with TWRP 2.2.2.1, FFF 1.4A and the latest version of CM 10 w/ SGT7 (9/05). Using KFU 0.9.6 when I attach my Kindle to my computer the ADB status is offline, while the drivers on my computer recognize it as an "Amazon Kindle Fire" and if I look in the properties I see "Amazon File-CD Gadget USB Device", "USB Mass Storage Device", and the drive it's recognized as "M:\" for me. No matter how often I attempt to reboot my computer, the Fire, or uninstall the drivers and install the drivers manually (either through the install drivers.bat or adding
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
and
0x1949
to android_winusb.inf and adb_usb.ini respectively.
However when I reboot my Fire into recovery, it's recognized as Online. Any help with getting it recognized when regularly booted up?
Sounds like a ROM issue. The new builds of CM10 have a PID of 0004 for some reason, rather than 0006.
Why it wouldn't affect recovery, though, I couldn't tell you.
Damn, alright. Thanks, at least I can always transfer a new ROM over and flash it when I need to. Hopefully they'll get it fixed soon.
Just use recovery to send adb commands.
soupmagnet said:
Just use recovery to send adb commands.
Click to expand...
Click to collapse
Right, I'm using it. I installed JandyCane and it's working just fine now. However I find I'm missing much of what I liked in the other ROM. Ah well, time to explore ROMs! Thanks for your help!
I added these 2 lines to the already long list of ids saved the win_usb file then reinstalled the driver now adb works
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
I finally got my Ouya. I installed the drivers following ouya's docs but when I run Ouya ToolBox, It can't detect my ouya Tried running as admin reinstalling drivers and restarting my pc but still nothing.
My goal is to install StockPlus rom for cifs support but I'm going out of my mind trying to detect it.
Am I forgetting something, anything I can do to fix this?
Regards,
Rick
Rick7C2 said:
I finally got my Ouya. I installed the drivers following ouya's docs but when I run Ouya ToolBox, It can't detect my ouya Tried running as admin reinstalling drivers and restarting my pc but still nothing.
My goal is to install StockPlus rom for cifs support but I'm going out of my mind trying to detect it.
Am I forgetting something, anything I can do to fix this?
Regards,
Rick
Click to expand...
Click to collapse
There's a "test" version, try it.
ElMeteK said:
There's a "test" version, try it.
Click to expand...
Click to collapse
I tried the test version and still a no go. I'm at a loss I have no idea what to do. I have never had a problem with my phones.
Rick7C2 said:
I tried the test version and still a no go. I'm at a loss I have no idea what to do. I have never had a problem with my phones.
Click to expand...
Click to collapse
Ok ToolBox 1.1.2 randomly started detecting my ouya I got it rooted...Now I'm trying to do the recovery however I don't have fastboot drivers and can't find them. OuyaToolBox said to use the same drivers as before but when I browse to that directory windows says it could not find the drivers for fastboot.
Rick7C2 said:
Ok ToolBox 1.1.2 randomly started detecting my ouya I got it rooted...Now I'm trying to do the recovery however I don't have fastboot drivers and can't find them. OuyaToolBox said to use the same drivers as before but when I browse to that directory windows says it could not find the drivers for fastboot.
Click to expand...
Click to collapse
Well I figured out how to bypass needing fastboot drivers and I am now in recovery only to find out I NEED a USB Keyboard well fml... I guess I gotta go buy a keyboard to flash my new rom.
Anyways I guess this can be closed/deleted.
could you please share how you got around needing fastboot drivers?
the ouya has a different hardware id when it is in fastboot mode. In fact, normal operation, recovery, and fastboot are all different hardware ids.
connect the ouya, adb fastboot, then go to the device manager, find the device and notice the hardware id change.
gotta go to the android_winusb.inf and edit it to match the new hardware id.
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_***&PID_****
^^^^ fill in the blanks.
OR!!! just separate the 3 different ids by commas.
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01, USB\VID_****&PID****, USB\VID_****&PID_****
see what i did there?
WooHoo!!
Finally got it
About time! Thanks guys
The only way I have been able to get adb working to OUYA is through editing the Windows driver manually this way (the first part) Open android_winusb.inf and add the following lines
beneath [Google.NTx86]:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
and then:
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
adb devices
But I know this is editing the Windows speicific generic driver that comes in the SDK. Does anyone know if I need to edit something like this on Ubuntu or how to get it connected to ADB on there? Thanks in advance for any help. I mainly use Ubuntu on a desktop, and my OUYA sits right beside that monitor and its MUCH easier to use Ubuntu, otherwise I have to sit at tihs computer with a laptop in my lap connected to the OUYA. So more of a convenience thing.
lemonoid said:
The only way I have been able to get adb working to OUYA is through editing the Windows driver manually this way (the first part) Open android_winusb.inf and add the following lines
beneath [Google.NTx86]:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
and then:
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
adb devices
But I know this is editing the Windows speicific generic driver that comes in the SDK. Does anyone know if I need to edit something like this on Ubuntu or how to get it connected to ADB on there? Thanks in advance for any help. I mainly use Ubuntu on a desktop, and my OUYA sits right beside that monitor and its MUCH easier to use Ubuntu, otherwise I have to sit at tihs computer with a laptop in my lap connected to the OUYA. So more of a convenience thing.
Click to expand...
Click to collapse
Yes, you still need to add the ouya ID to adb_usb.ini. Assuming you have a ~/.android/ directory, use this command to add the ID.
Code:
echo 0x2836 >> ~/.android/adb_usb.ini
I was setting up adb to fix the wifi on hashcodes 4.3 rom.....after i got it set up i tried to run it but it wouldnt run adb shell fix-mac.sh without being in the platform-tools folder....(yes my drivers are installed) and it asked for root#otter when i entered the command....supersu is set to allow commands from the computer and i dont know what to do...i dont want to switch roms...and yes i just reinstalled my drivers (they werent working before).Can anybody tell me whatt to enter in after that or a way around it?
Go to developer options and enable Android Debugging. On your computer does it come up Android Composite ADB Interface? If not it is likely that modifications will have to be done to the win_usb.ini file and the driver reinstalled. Also when it is fixed you should see a prompt on your kindle screen to allow ADB from your computer specifically. Here is where you can find answers to resolve most issues with ADB http://forum.xda-developers.com/showthread.php?t=2179748 .
Thepooch said:
Go to developer options and enable Android Debugging. On your computer does it come up Android Composite ADB Interface? If not it is likely that modifications will have to be done to the win_usb.ini file and the driver reinstalled. Also when it is fixed you should see a prompt on your kindle screen to allow ADB from your computer specifically. Here is where you can find answers to resolve most issues with ADB http://forum.xda-developers.com/showthread.php?t=2179748 .
Click to expand...
Click to collapse
His thread isn't relevant as I installed the drivers (it said the drivers were adb composite interface) via windows update and I used android SDK for other things..my kindle does show up in adb devices and I do have USB debugging right now...I don't have access to my backup laptop right now (my backup laptop has everything on it and runs windows xp) and my main laptop is how can I word it.....dead so I can't check what it shows up as
Jacobloveskindles said:
His thread isn't relevant as I installed the drivers (it said the drivers were adb composite interface) via windows update and I used android SDK for other things..my kindle does show up in adb devices and I do have USB debugging right now...I don't have access to my backup laptop right now (my backup laptop has everything on it and runs windows xp) and my main laptop is how can I word it.....dead so I can't check what it shows up as
Click to expand...
Click to collapse
So what are you doing? You have me confused and I can resolve about 90% of driver related issues. I could always look then it doesn`t have to be guessing game .
Thepooch said:
So what are you doing? You have me confused and I can resolve about 90% of driver related issues. I could always look then it doesn`t have to be guessing game .
Click to expand...
Click to collapse
I was just saying I'll check if it says adb composite interface when I plug it in into my backup laptop in the morning
Jacobloveskindles said:
I was just saying I'll check if it says adb composite interface when I plug it in into my backup laptop in the morning
Click to expand...
Click to collapse
Ahh got ya.
Thepooch said:
Ahh got ya.
Click to expand...
Click to collapse
Well when I plug it in it shows up as this: http://m.imgur.com/7d3tIdJ but in device manager it shows this: http://m.imgur.com/GlQZLnS
I'm running windows xp pro 32-bit and my kindle is (you know) on hashcodes stock 4.3 ROM and I'm trying to issue the WiFi fix command
I have superSU installed from recovery and usb debugging enabled...although i don't think it matters it has cotr recovery installed
Jacobloveskindles said:
Well when I plug it in it shows up as this: http://m.imgur.com/7d3tIdJ but in device manager it shows this: http://m.imgur.com/GlQZLnS
I'm running windows xp pro 32-bit and my kindle is (you know) on hashcodes stock 4.3 ROM and I'm trying to issue the WiFi fix command
I have superSU installed from recovery and usb debugging enabled...although i don't think it matters it has cotr recovery installed
Click to expand...
Click to collapse
No it doesn`t matter that you have COTR installed I see that is shows up as android adb interface that is the incorrect facet of a multi-faceted driver. it is appear as if the device is in fastboot. It needs to read Android Composite ADB Interface. Right click where it sad Android ADB Interface select update driver then point it to the driver folder in KFU. XP is inherently difficult to make this happen several things need to be in place to force it to work because it refuses often to install a driver that is Unsigned. Right click on Android ADB interface select properties, then hardware id. Make sure the correct VID and PID matches are in the android_winusb. ini .
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0001
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
Code:
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
If not add them, then click save make sure there is a copy of this in your .android folder as well as a copy of the adb_usb. conf with is line inside 0x1949 then reinstall the driver by pointing it to the driver do not allow Microsoft to help you with the update it is pointless simply just direct the installation to the driver folder skip searching update and it may install. Sometimes you must uninstall then reinstall to get it right. As you can see there is alot more to it. If it comes up with this code
Code:
0123456789 offline
instead of
Code:
0123456789 device
when you
Code:
adb devices
your not there yet so keep trying or let a pro in there to help you fix it . Watch for the prompt on your kindle screen to allow adb specifically from your computer. Good luck.
Thepooch said:
No it doesn`t matter that you have COTR installed I see that is shows up as android adb interface that is the incorrect facet of a multi-faceted driver. it is appear as if the device is in fastboot. It needs to read Android Composite ADB Interface. Right click where it sad Android ADB Interface select update driver then point it to the driver folder in KFU. XP is inherently difficult to make this happen several things need to be in place to force it to work because it refuses often to install a driver that is Unsigned. Right click on Android ADB interface select properties, then hardware id. Make sure the correct VID and PID matches are in the android_winusb. ini .
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0001
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0001&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
Code:
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0100
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0100&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&REV_0216&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0007&MI_01
If not add them, then click save make sure there is a copy of this in your .android folder as well as a copy of the adb_usb. conf with is line inside 0x1949 then reinstall the driver by pointing it to the driver do not allow Microsoft to help you with the update it is pointless simply just direct the installation to the driver folder skip searching update and it may install. Sometimes you must uninstall then reinstall to get it right. As you can see there is alot more to it.
Click to expand...
Click to collapse
I used the found new hardware wizard to reinstall the drivers from kfu because those drivers didn't install for me this was before...and yes the kfu drivers said they were unsigned.I also have the android SDK installed if that helps...you are confusing me....before I had the drivers installed it showed up as mtp...I'm not in fastboot I'm in the ROM when I plug it in.....please help me..not..be..confused
Jacobloveskindles said:
I used the found new hardware wizard to reinstall the drivers from kfu because those drivers didn't install for me this was before...and yes the kfu drivers said they were unsigned.I also have the android SDK installed if that helps...you are confusing me....before I had the drivers installed it showed up as mtp...I'm not in fastboot I'm in the ROM when I plug it in.....please help me..not..be..confused
Click to expand...
Click to collapse
I can fix your problem not your confusion best you let me show you. PM sent unread your private messages.
Thepooch said:
I can fix your problem not your confusion best you let me show you.
Click to expand...
Click to collapse
K.show me :cyclops::good: (I'm bored right now...sorry)
Jacobloveskindles said:
K.show me :cyclops::good: (I'm bored right now...sorry)
Click to expand...
Click to collapse
Unread your private messages.