I am trying to install the Cynogenmod 12 ROM on my Ouya. One of the prerequisites is the Ouya Bootmenu, which requires a recent ClockworkMod to be installed.
I have ADB installed.
On my Windows PC, I type "adb reboot recovery" and my Ouya reboots to a screen that says OUYA with a red exclamation mark.
On the OUYA, I hit my HOME key, and select to sideload from ADB. Yellow text appears on my OUYA screen that says "Now send the package you want to apply to the device with "adb sideload <filename>" ..."
Back on the Windows PC, I try typing "adb sideload recovery-clockwork-6.0.4.8-ouya.zip" and get "error: device not found".
It appears that the OUYA isn't visible to the PC when it is in recovery mode, which seems to be a bit of a problem.
Well you might get told this is the wrong section for this question but I'll just try and answer here.. The red ! is stock recovery so sideloading probably won't work, you'll have to follow instructions HERE to ensure adb is working and superuser is good, then I personally used the manual method HERE to get CMW installed, finally you just flash the boot menu zip and you're good to go!
The issue was that the CWM was getting over written every time the OUYA booted.
By deleting all the partitions, and then installing Bootmenu, CWM, and the new ROM without rebooting I kept it from doing that.
Related
hello
somehow my internal sd card got wiped after i wiped my system in trwp recovery'
now im stuck in recovery and i tried to adb sideload and adb push the rom zips but neither works, if i type "adb devices" it gives me a blank space and adb push says it cant find any device
i reinstalled htc sync and all and all the SDK packages but nothing helps
any suggestions?
shiyou said:
hello
somehow my internal sd card got wiped after i wiped my system in trwp recovery'
now im stuck in recovery and i tried to adb sideload and adb push the rom zips but neither works, if i type "adb devices" it gives me a blank space and adb push says it cant find any device
i reinstalled htc sync and all and all the SDK packages but nothing helps
any suggestions?
Click to expand...
Click to collapse
when in recovery, what does Windows Device Manager show? can you check my guide under FAQ#2 if that solves it for you.
nkk71 said:
when in recovery, what does Windows Device Manager show? can you check my guide under FAQ#2 if that solves it for you.
Click to expand...
Click to collapse
it shows One in exclamation symbol
i followed ur guide in faq #2 but i cant find "Android USB Devices"
ok somehow everything worked out with ur guide thx!!
FYI: I am not tech savy at all so bare with me if I sound like a noob/idiot.
I basically formatted my phone from TWRP and I'm thinking there isn't any ROM/UI/kernel?..ect. so it cannot start up (basically stuck on the htc loading screen). My computer detects it but not as a storage device and I can't seem to find a way to access it. I believe I have what i need on my computer but my issue is that i dont know how to get into the internal storage of my htc one because it cannot detect it as a storage device on my computer.
The only trace of it at all i seem to be able to find is in
Control Panel\Hardware and Sound\Devices and Printers
Its called "android 1.0" and when i click on it, it takes me to its properties from device manager.
It says Location: Port_#0001.Hub_#0008
I dont know if any of this info i gave is relevant, if not, let me know what ups.
ray408 said:
FYI: I am not tech savy at all so bare with me if I sound like a noob/idiot.
I basically formatted my phone from TWRP and I'm thinking there isn't any ROM/UI/kernel?..ect. so it cannot start up (basically stuck on the htc loading screen). My computer detects it but not as a storage device and I can't seem to find a way to access it. I believe I have what i need on my computer but my issue is that i dont know how to get into the internal storage of my htc one because it cannot detect it as a storage device on my computer.
The only trace of it at all i seem to be able to find is in
Control Panel\Hardware and Sound\Devices and Printers
Its called "android 1.0" and when i click on it, it takes me to its properties from device manager.
It says Location: Port_#0001.Hub_#0008
I dont know if any of this info i gave is relevant, if not, let me know what ups.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Here is some reading material for you
Bro..I completely understand your predicament..
Just do this step by step
1. Download minimal adb from the internet and install it on your PC.
2. Download twrp image from the internet.this is a recovery loader.
3.copy the image file into the install directory of minimal adb.
4.execute the minimal adb shortcut from your PC.it should open a command prompt.
5.connect your device to the PC via usb.
6. Type this command to check if your device is recognized. "Fastboot devices"
It should show you a device ID..if your device is connected and recognized
7.flash tarp image with this command "fastboot flash recovery <twrp.img>"
8.reboot your device..press and hold volume down at the sametime to get into bootloader.
9.enter recovery.
10.Download any custom rom from htconeroot.com.it will be a zip file.
11. Copy the zip into minimal adb install directory and run this command to push the zip onto your device. "adb push <image file>.zip any name.zip"
12. After this completes you should be able to see this image in the filemanager in twrp.
13.move the zip file into sdcard directory.
14.make sure all options are checked in the mount in twrp
15.install the custom rom from install option in tarp.
This is 3 frantic days of research on the internet bro..
I had a brick in my hand too..got it up and running VIPERONE ROM
Hope you get through this fine
Thank you, i really appreciate the effort! but im stuck on step 6/7. When i typed in fastboot devices, it didn't show any new id. and when i typed fastboot flash recovery twrp.img it says "waiting on device" so im guessing it still didnt detect it. any idea on why this might be happening? thanks
gowda-the-grear said:
Bro..I completely understand your predicament..
Just do this step by step
1. Download minimal adb from the internet and install it on your PC.
2. Download twrp image from the internet.this is a recovery loader.
3.copy the image file into the install directory of minimal adb.
4.execute the minimal adb shortcut from your PC.it should open a command prompt.
5.connect your device to the PC via usb.
6. Type this command to check if your device is recognized. "Fastboot devices"
It should show you a device ID..if your device is connected and recognized
7.flash tarp image with this command "fastboot flash recovery <twrp.img>"
8.reboot your device..press and hold volume down at the sametime to get into bootloader.
9.enter recovery.
10.Download any custom rom from htconeroot.com.it will be a zip file.
11. Copy the zip into minimal adb install directory and run this command to push the zip onto your device. "adb push <image file>.zip any name.zip"
12. After this completes you should be able to see this image in the filemanager in twrp.
13.move the zip file into sdcard directory.
14.make sure all options are checked in the mount in twrp
15.install the custom rom from install option in tarp.
This is 3 frantic days of research on the internet bro..
I had a brick in my hand too..got it up and running VIPERONE ROM
Hope you get through this fine
Click to expand...
Click to collapse
ray408 said:
Thank you, i really appreciate the effort! but im stuck on step 6/7. When i typed in fastboot devices, it didn't show any new id. and when i typed fastboot flash recovery twrp.img it says "waiting on device" so im guessing it still didnt detect it. any idea on why this might be happening? thanks
Click to expand...
Click to collapse
Ok..try this..
Press down on the power and volume down button to enter the default boot loader.
If you hv rooted your phone..it should be showing tampered at the top.
select the fast boot option..
Now connect your phone via usb..
The display name should change to "fastboot usb"
Then again open minimal adb and continue from step 6.
Make sure you have all the htc drivers for Windows installed on your PC.
Windows can automatically download these drivers for you if you don't have them..
All the best
Are you using Windows 8.1?
everything works now, thank you guys. You are all awesome!
Hello,
My nexus 6 was rooted and with TWRP. However, while trying to update to 5.0.2 using this ROM (http://forum.xda-developers.com/nexus-6/development/rom-pure-shamu-beta-2-0-t2952604), I ended up with no OS on it. I can boot into TWRP just fine.
So I am trying to sideload the ROM and rest of the files, however, my Win 8.1 shows "device not found". The command "adb devices" show no devices as well.
Win 8.1 device manager shows the phone as "Google Nexus ADB Interface" with driver ClockworkMod 8/27/12 7.0.0.4.
Any ideas?
Reinstalling and selecting from list did the trick, the device is listed as "Android Composite ADB Interface".
However, I must be missing something too obvious that I just cannot see...
I go into TWRP
go into advanced
go into ADB sideload and enable it
on PC, "adb device" will list it "recovery"
on PC, "adb sideload filename.zip" give me "error: Protocol fault (no status)"
then found out I had to stop the process "adb", which I do now.
Now when sideloading the zip I get "error: closed"
Ok, who knows why it was not working, but ended up doing a push instead, then I just installed via TWRP the ROM, gapps and SU.
Command I used: adb push rom.zip /data/media/rom.zip
this thread sounds like what I do when my mom has a question about something. Leave her alone for awhile and she finds the answer her self.
My device is Moto X (XT1060). I wiped my Internal storage, Cache, Data, System entirely.
I went to my TWRP v2.6.3.1 recovery and tried to sideload cm12.zip via adb.exe but it failed to recognize the device.
I tried
Code:
adb sideload cmfile.zip
but it show's
Code:
error: device not found
I installed Motorola Device manager.. but no luck so far.
I think I need drivers or something for XT1060.. Please help me.
You should search for twrp 2.8.4.0 for Moto X 2013. Also, make sure you have the latest android SDK and ADB files installed. You'll need to search for threads that help get your phone connected to a pc.
Or you could use 'adb push cm12.zip /sdcard' (without the apostrophes) in a cmd prompt then flash in recovery. Why does everyone resort to sideloading when there's any easier method that will always work?
Once you get your Android SDK and drivers set up and storage mounted in recovery.
nhizzat said:
Or you could use 'adb push cm12.zip /sdcard' (without the apostrophes) in a cmd prompt then flash in recovery. Why does everyone resort to sideloading when there's any easier method that will always work?
Once you get your Android SDK and drivers set up and storage mounted in recovery.
Click to expand...
Click to collapse
or you can boot your phone into bootloader if you can and flash the device back to stock and start over.
nhizzat said:
Or you could use 'adb push cm12.zip /sdcard' (without the apostrophes) in a cmd prompt then flash in recovery. Why does everyone resort to sideloading when there's any easier method that will always work?
Once you get your Android SDK and drivers set up and storage mounted in recovery.
Click to expand...
Click to collapse
That is basically all the sideload command does isn't it? I seemed to notice when I side loaded I was left with the zip I installed on my device... I could swear I deleted it manually, which would mean that sideload just pushes and installs for you in once nice package.
Either way, the issue he is having is that ADB won't find his devices... read the error message its not having trouble with the sideload or the zip... He just doesn't know how to use ADB and make it recognize his device...
Pushing doesn't always work when ADB doesn't recognize your device....
Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
I type adb devices and it comes back null. I've tried killing and restarting the daemon server and that isn't it. I've tried uninstalling and reinstalling the drivers. There is even an ADB composite driver listed in the device manager and yet once the tablet is in recovery mode it seems to disappear.
I tried doing a factory reset and wiping the cache. i'm drawing a blank on this. I've also tried changing usb ports and cables on the computer. It's just not working.
Any ideas?
You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..
There are two options to restore stock at the bottom of this link, it all depends what version you have. See if it helps...
http://forum.xda-developers.com/showpost.php?p=62986666&postcount=4
or you could also try this to get into Amazon Custom recovery:
adb reboot recovery
Yeah, most likely a driver issue. Try different drivers until you find one that actually works!
Well I just thought of this when I woke up, could it be that I'm using minimal ADB and fastboot or should that not make a difference?
As long as your device is listed when doing a "adb devices" or "fastboot devices" should make no difference. But yes, minimal should be fine.
But it is usually a good idea to have the latest version.
I think your issue is with getting to Amazon recovery. If in recovery, there should be a menu. See that menu here in post #3:
http://forum.xda-developers.com/amazon-fire/general/amazon-fire-2015-tips-tricks-t3214544
Tuvan03 said:
Ok I've been at this for hours trying to get adb to recognize the tablet in recovery mode and to no avail. I've tried every trick and random driver i can find on here and still am unable to get adb to recognize the tablet while waiting for a sideload .bin file. While in normal mode while up and running adb devices command find sit np but once it goes into recovery it's gone.
Click to expand...
Click to collapse
You're talking 2 different modes here: (1) Recovery mode: You see menu options on tablet. Windows can't ever recognize device while in recovery mode; no driver appears in Win Device Manager. (2) Sideload mode: After you select "apply update from ADB" and press power button and you see yellow text on tablet saying to sideload the file. Fire appears in Device Manager. If no driver installed (or messed up), it's under "Other" with the name KFFOWI as @gray-beard said. That's what you need to install drivers for in order for sideload to work. I doubt Minimal adb is the problem. You're probably just not all the way into sideload mode. If problems persist, open the console window from the folder containing adb.exe.
gray-beard said:
You may need to disable driver signature enforcement
then install drivers.
After that you may still need to follow this guide
http://forum.xda-developers.com/showpost.php?p=62561874&postcount=2
This was written for a different FIRE so yours will be KFFOWI instead of KFARWI in the guide.
I did this and in worked for me..
Click to expand...
Click to collapse
Many Thanks Gray Beard, it's reloading the stock firmware now. I was just trying to go through the pick your device drivers thing too quickly and needed to do the see all devices to be able to see the adb drivers to get them loaded.
A pint of the finest dwarven ale to you (with a name like gray beard i couldn't resist)
EDIT: I did all this just to try to restore OTA updates, yet i hit the update button now that it's restored with the factory firmware and it's saying no updates found. hmm