I started off slow, I had my OUYA fully updated, I used the OneClick Recovery, went fine. Then I threw the "RootMyOUYA" apk on it, all went fine. I decided to put Xposed Framework on it, fine, Mod Collection, fine.
I did a Factory Reset just to get a clean slate, I loaded the OUYA back up and logged into my account. I went back into recovery, wiped Cache & Dalvik, flashed StockPlus. It was SUPER delayed and laggy trying to navigate menus. I tried doing a Factory Reset but it did nothing. I went back into recovery and did a data/factory reset, cache, dalvik wipe and now...
I get the OUYA splash screen, background, and then black screen. Nothing. How do I fix this?
If it helps at all, its still recognized under ADB.
EDIT:
HOW TO RECOVER:
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Once you get to the recovery menu, the select the second option to update from adb. Download the OTA update from the link at the end of this post, and run the command "adb sideload RC-OUYA-1.0.193-r1_ota.zip" this will reformat the system partition and reinstall the ouya software. You might also want to do a factory reset before rebooting.
Links to download the OTA updates can be found on this xda thread: http://forum.xda-developers.com/showthread.php?t=2266629
Click to expand...
Click to collapse
Now no longer recognized under ADB... Any ideas?
If you are able to connect via ADB during boot you can ADB reboot recovery then flash a rom. If you can not connect via adb try to get to recovery manually. All you have to do is plug in a PC keyboard via USB and restart the ouya. Now press the keys alt + i + sysrq for 4-6 seconds then let go for about half a second and repeat the key press for some time.
It might take you some attempts but eventually recovery should show up.
If you wonder sysrq is print on most keyboards. Now you should be able to adb and flash ROMs.
Gesendet von meinem One X+ mit Tapatalk 4
nchantmnt said:
If you are able to connect via ADB during boot you can ADB reboot recovery then flash a rom. If you can not connect via adb try to get to recovery manually. All you have to do is plug in a PC keyboard via USB and restart the ouya. Now press the keys alt + i + sysrq for 4-6 seconds then let go for about half a second and repeat the key press for some time.
It might take you some attempts but eventually recovery should show up.
If you wonder sysrq is print on most keyboards. Now you should be able to adb and flash ROMs.
Gesendet von meinem One X+ mit Tapatalk 4
Click to expand...
Click to collapse
Yeah I wound up figuring it out. My derpderp-self forgot to put USB Debugging back on after I got everything set up. All is good now! :good:
Related
Need a bit of help here..
I have been playing a bit with my Ouya, installed SuperSU etc, everything worked fine, until I decided to reboot it.
Now it won't boot anymore. When I start it, my TV stays black. I only see some white dots and occasional a greenish flash..
What could I do now?
Dropshots said:
Need a bit of help here..
I have been playing a bit with my Ouya, installed SuperSU etc, everything worked fine, until I decided to reboot it.
Now it won't boot anymore. When I start it, my TV stays black. I only see some white dots and occasional a greenish flash..
What could I do now?
Click to expand...
Click to collapse
Same here any help?
Dropshots said:
Need a bit of help here..
I have been playing a bit with my Ouya, installed SuperSU etc, everything worked fine, until I decided to reboot it.
Now it won't boot anymore. When I start it, my TV stays black. I only see some white dots and occasional a greenish flash..
What could I do now?
Click to expand...
Click to collapse
If adb still connects and assuming you have installed CWM and have a backup, just run:
adb reboot recovery
then flash your backup.
deathknight842 said:
If adb still connects and assuming you have installed CWM and have a backup, just run:
adb reboot recovery
then flash your backup.
Click to expand...
Click to collapse
adb does still connects, but did not yet install CWM..
Dropshots said:
adb does still connects, but did not yet install CWM..
Click to expand...
Click to collapse
I found a fix.. http://forums.ouya.tv/discussion/1380/recovery-mode
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Once you get to the recovery menu, the select the second option to update from adb. Download the OTA update from the link at the end of this post, and run the command "adb sideload RC-OUYA-1.0.193-r1_ota.zip" this will reformat the system partition and reinstall the ouya software. You might also want to do a factory reset before rebooting.
Links to download the OTA updates can be found on this xda thread: http://forum.xda-developers.com/showthread.php?t=2266629
Click to expand...
Click to collapse
same here... i posted this -> http://forum.xda-developers.com/showthread.php?t=2318169
but the recovery mode from the post above does not work
when i run adb shell it says error: device not found.. so i guess i am F**KED
Maybe a factorycable can get the Ouya into fastboot like the Kindle fire hd?
Sent from my C6603 using xda app-developers app
Dogie52 said:
Same here any help?
Click to expand...
Click to collapse
when you turn it on, with a usb cable plugged in, will it still pop up as a drive?
When I installed SU/busybox/CWM yesterday I noticed that both fastboot and recovery turn up as different devices in windows from the usual ADB one. I forced windows to install the ADB driver for them and it worked fine then.
This thread is three weeks old, I'm sure they figured something out.
Sent from my GT-P3113 using Tapatalk 4 Beta
muppetterror said:
same here... i posted this -> http://forum.xda-developers.com/showthread.php?t=2318169
but the recovery mode from the post above does not work
when i run adb shell it says error: device not found.. so i guess i am F**KED
Click to expand...
Click to collapse
Try to sideload the newest update. When you are in original recovery there is no way to get a web shell. Had the problem to.
I did the web wireless setup and got stuck on black screen after reboot. The I did the sideload and installed the update and everything works fine again.
Sent from my HTC One using xda premium
is this still happening or is it fixed now?
Dogie52 said:
I found a fix.. http://forums.ouya.tv/discussion/1380/recovery-mode
Click to expand...
Click to collapse
This method worked for me. I had some issues with the key sequence at first, but tried it a few times and I was able to get into stock recovery. Once there I had an issue with adb seeing my Ouya, the trick was reinstalling the Google usb drivers using the "I have disk" method in Windows device manager.
I was able to fully flash the latest ota update through adb sideload and got it working.
Now, onto rooting and cwm.
Best of luck!
Sent from my SCH-I535 using Tapatalk 2
So I had clockworkmod installed andworking beautifly but now the update for the ouya is messing things up. It goes to update and install then during reboot it boots to clockworkmod and no update is installed. I cant cancel the update and do anything with the ouya because of this. Anyone have any ideas? also The cwm looks funky again http://forum.xda-developers.com/showthread.php?t=2369317 as seen here from another thread of mine. I was able to get it to look normal with a manual flash of cwm but when it does this update and reboots cwm looks like that.
Thanks in advance
I ran into the same problem with the last 2 updates with clockworkmod, and ended up plugging in an old USB keyboard. When it booted to clockworkmod I could then navigate through a messed up looking screen and pick the correct option to accept the update.
The latest update didn't work like that, though. It came through 12/3 or 12/4? It would reboot and I kept losing video, then would power back up and redownload with the video on and off. To fix that I ended up following these directions and doing a reset. Then it did the update, and )I believe) reloaded the stock recovery. At least it works now, though...
forums.ouya.tv/discussion/1380/recovery-mode
HOW TO RECOVER:
This is a hack, an unintended sequence of events that results in recovery mode; what you need to do is crash the startup using sysrq.
For this you'll need a usb keyboard with the sysrq key, this is usually the printscreen button if your keyboard isn't labeled. As the OUYA starts to boot, hold down the alt-sysrq keys and press i, wait a few seconds and then repeat. This key combination is kill-all-tasks; thanks to whoever left this enabled in the kernel. Each time you kill the tasks the init process will restart them, after about 5 or 6 times init will print a warning on the console that one of the processes marked critical has been restarted too many times -- this then triggers an automatic reboot into recovery mode.
Unfortunately it's not always obvious when the ouya is in recovery mode. You might get screen with the ouya logo and a large red exclamation mark, or the screen might be entirely black; usually I got a black screen. Press the home button on the keyboard to bring up the recovery menu; it's actually a toggle so feel free to press the home button repeatedly until you see the menu since the timing isn't otherwise obvious.
Click to expand...
Click to collapse
The phone is in bootlopp (i think).When i turn on appears android on groundb with the red triangle and a chinese word.This disappears and appears again,for an infinite time.Display stays turned on.Turning on in bootloader it works,but just in bootloader.If i try to enter in "Restart bootloader,"recovery,"normal boot"ecc it's in bootloop again.So i can access only bootloader at the moment.I want to reflash system,droidboot imgs ecc with fastboot but...tried to recognize phone on an old HP Compaq nx6110 with usb 2.0 and win7.installed on it adb drivers,adb and fast-tools.don't think zenf2 drivers are important at the moment,now should consider just the adb drivers cause i can access only bootloader.however i think zenf2 drivers are installed on it.nothing.phone no recognized by fastboot and no recognized by windows.consider that on a xp and 2.0 usb pc (with fastboot,adb,and adb drivers on it) phone is recognized by windows as Android-Phone but then windows says i've not the drivers for the installation (appears the drivers' choosing window).No asus driver on it,on the win7 pc there are!!
CenereZar said:
The phone is in bootlopp (i think).When i turn on appears android on groundb with the red triangle and a chinese word.This disappears and appears again,for an infinite time.Display stays turned on.Turning on in bootloader it works,but just in bootloader.If i try to enter in "Restart bootloader,"recovery,"normal boot"ecc it's in bootloop again.So i can access only bootloader at the moment.I want to reflash system,droidboot imgs ecc with fastboot but...tried to recognize phone on an old HP Compaq nx6110 with usb 2.0 and win7.installed on it adb drivers,adb and fast-tools.don't think zenf2 drivers are important at the moment,now should consider just the adb drivers cause i can access only bootloader.however i think zenf2 drivers are installed on it.nothing.phone no recognized by fastboot and no recognized by windows.consider that on a xp and 2.0 usb pc (with fastboot,adb,and adb drivers on it) phone is recognized by windows as Android-Phone but then windows says i've not the drivers for the installation (appears the drivers' choosing window).No asus driver on it,on the win7 pc there are!!
Click to expand...
Click to collapse
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
samteeee said:
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
Click to expand...
Click to collapse
Thank you bro,you saved me
samteeee said:
When you see the dead android with red triangle, hold the power button and keep pressing it and quickly
press volume up button and release it but keep the power button and you will see the Recovery options.
Then choose "format Cache" with volume up & down button and enter with power button to format cache partition.
It would take a long time so don't be alarmed. When done, choose restart system and the boot loop should be fixed.
Good luck.
Click to expand...
Click to collapse
Didn't work for me ... if I keep pressed the power button for a long time, power off the phone and it doesn't entry in Recovery mode...
I resolved with "fastboot erase cache" command
It is normal to get that error when selecting 'recovery mode'
The next step is a little tricky. You have to press and hold the power button, then press the volume up button. It may take a few tries. Both buttons will have to be pressed together simultaneous to enter Android system recovery. Please also see http://www.asus.com/us/support/FAQ/1011956/
Sincerely,
ASUS_USA
Asus_USA said:
It is normal to get that error when selecting 'recovery mode'
The next step is a little tricky. You have to press and hold the power button, then press the volume up button. It may take a few tries. Both buttons will have to be pressed together simultaneous to enter Android system recovery. Please also see http://www.asus.com/us/support/FAQ/1011956/
Sincerely,
ASUS_USA
Click to expand...
Click to collapse
Hi,
I´m having a problem with mine. Can´t recognize phone in fastboot but it´s different. I already asked for help in general thread - all resources (page 47 to 50) but still can´t solve.
I rooted my device using method 3 (one click root) and first everything seems fine, but on my first reboot i entered on bootloader - recovery and started a wipe cache, but didn´t finished it, push power button and force it of (i seemeed stuck there - was wipping for more than 10 minutes). Since then i can´t solve anything, tried many ways to unbrick my phone but i seem the problem was i can´t connect fastboot. After a lot o tries, i entered in TWRP using method 2 and wipe, made a recovery, everything and as magic i can enter again on recovery, even tried adb sideload (it started, but when starts to write something - at 50% of the process just ended). So, long story short, i did a flash of the original firmware i downloaded from asus website using method 2 and now it´s working as original, but i still having the same problem (or maybe worst, since i can´t enter the TWRP recovery using method 2 anymore) and can´t root my device. When i tried to do anything using fastboot it´s just shows "FAILED", When i request adb devices shows a blank line. If my phone is on, using android, it shows the correct serial number.
I don´t know what´s happening, it seems to estabilsh a connection (when on its ok, method 2 freeze on teamwin logo - the tool can write something on phone) but can´t write anything. i´m worried because i think i won´t be able to do any update and i wanted a rooted phone to.
Anyone seems a solution?
I'm having the same problem today and I solved it just now! I can't even open the fastboot and recovery. Finally I install the software "shuame"(I'm Chinese, you guys may find other software) on my PC, and with it my computer read zenfone2, and I use the function in the software to open fastboot mode, then I flash the WW version recovery.img and boot.img with a one-click tool in zentalk(TW), then I just double wipe, the phone is alive now !
Sent from my ASUS_Z00AD using XDA Free mobile app
ityoung said:
I'm having the same problem today and I solved it just now! I can't even open the fastboot and recovery. Finally I install the software "shuame"(I'm Chinese, you guys may find other software) on my PC, and with it my computer read zenfone2, and I use the function in the software to open fastboot mode, then I flash the WW version recovery.img and boot.img with a one-click tool in zentalk(TW), then I just double wipe, the phone is alive now !
Sent from my ASUS_Z00AD using XDA Free mobile app
Click to expand...
Click to collapse
I don´t know any other software. Is this software only in chinese ? Can i try?
My phone is actually working, but i can´t flash anything, even MOFD_update.zip (the file it is used to make ota uptades)
is Your phone rooted? which method did you use? Now you can use fastboot normally?
This is a new on me. I booted into recovery mode after an update (which took just fine), and now that I'm in Recovery Mode, I'm stuck. The power button is acting like it doesn't work, but it does since I was able to boot into Recovery Mode! Up and Down buttons work just fine and I can seemingly "select" an option (the line text background changes from blue to green)..but nothing happens. I can't even seem to force another reboot. Any ideas?
Plug it into a PC and try running the command "adb reboot" without the quotes in command prompt.
kael41 said:
This is a new on me. I booted into recovery mode after an update (which took just fine), and now that I'm in Recovery Mode, I'm stuck. The power button is acting like it doesn't work, but it does since I was able to boot into Recovery Mode! Up and Down buttons work just fine and I can seemingly "select" an option (the line text background changes from blue to green)..but nothing happens. I can't even seem to force another reboot. Any ideas?
Click to expand...
Click to collapse
Have you tried Vol down + Power button for up to 15 seconds to see if that will reboot the device?
Sent from my [device_name] using XDA-Developers Legacy app
This happened to me as well. Power button works for selecting an option by double pressing it twice quickly.
I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.
veryspecialagent said:
I searched and didn't see anything that relates to my specific problem.
I have a 1952-4 that I rooted per instructions on here (Magisk). I dropped it and broke the screen about 9 months ago and just fixed it today...and I can't remember my pattern. I'm up to 50 tries, so now I have to wait 120 seconds before it lets me try the next one.
Since the root process requires you to reboot recovery for root, doing that just sends it to the normal lock screen. When I hit Vol Down/Power, my options on the bootloader screen are:
-Start
-Restart Bootloader
-Recovery Mode (restarts it, sends to lockscreen)
-Power Off
-Factory Mode (restarts, sends to lockscreen)
-Barcodes
-BP Tools (restarts, back to lockscreen)
-QCOM (restarts, back to lockscreen)
-Bootloader Logs
-Switch Tools Mode (enables/disables "Tool Mode Config" option on the bootloader screen)
My computer beeps the "something USB has been plugged in" chime when I connect it, but it doesn't pull up in File Explorer (unless it's off, but just shows that a USB drive has been connected but won't pull up anything when I click on it), nor can I connect through ADB. It's not a cable/USB port issue either as ADB finds my Note 8 when I plug it in and check via "adb devices."
Can't wipe it via Find my Phone either because it's been 270 days since my account pinged the phone, so it just shows up as "Android" device.
Any suggestions on how to either get my computer/ADB to recognize it (with root) so I can just delete the lock database, or how I can factory reset it? Am I forgetting a reboot option?
Thanks in advance.
Click to expand...
Click to collapse
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot
sd_shadow said:
In Bootloader
factory reset with
Code:
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.
veryspecialagent said:
I'm on the bootloader screen (PWR/Vol-)
Computer does not show it connected, either in FIle Explorer or ADB.
Click to expand...
Click to collapse
Window 10?
Yeah. It should remember this phone, since I used this computer to root it when I first got it a year and a half ago.
I used a different cable and got it to pick up the phone (as an unknown device) in Windows but NOT ADB, and the phone to realize it was connected (see last line on phone screen) but they're not talking.
If I boot it all the way up, either regular or recovery (root), it doesn't show at all on my computer.
Like I said, I'd be fine with wiping it, but can't even get to that option.
Install the moto drivers. If that doesn't work then make sure your using a usb2 port and not a usb3 port as its a known issue with moto phones.
I just ordered a new OEM cable.
Also ordered an OTG cable to see if I can force it to startup into a different mode that'll allow me to do something with it.
I'll update this thread once I'm able to test them out.
I got a new cable. My USB ports are not labeled, and my Moto drivers reinstalled.
After rebooting to the recovery screen, I plugged it in and apparently I have fastboot. I checked the bootloader logs and it says:
AP Fastboot Flash Mode (Secure)
Fastboot Reason: Volume down key pressed
USB connected
Windows doesn't pick up anything connected by USB. I can't restart to get root because then adb doesn't pick up the phone either because of the screenlock preventing me from hitting ok to trust my computer.
I'm asking the following because I can't find answers: Can you delete the screen lock file with the only bridge being fastboot, not adb. How can I do a factory reset if rebooting to recovery is our normal way of turnin gon the device with root access? Or would reflashing something work?
command line commands are a perishable skill and it's been a couple years since I did this stuff.
Thanks in advance.
To recap, I either need to be able to get into the directory to delete the pattern lock, or factory reset the phone.
I've tried the pattern lock 79 times, which means I have to wait 300+ seconds between tries. I think an error is causing that though.
Fastboot is my only option at this point as far as using commands goes. Rebooting recovery just reboots it with root permissions, but neither adb or Windows 10 picks it up. Using a brand new factory cord and tried every USB port on my computer, even the USB-C to USB-C. But I can't find anywhere that shows how to get into the directory using fastboot.
In Device Manager, I've been getting an error with Android ADB Interface (The device cannot start; Code 10). I uninstalled, reinstalled various drivers, killed adb.exe, etc., Still happening.
HOWEVER, Motorola ADB Interface is working just fine and goes away when I unplug my phone, returns when I plug it in. Only when it's in recovery/fastboot mode though.
I got into Safe Mode, but computer won't pick it up.
I can't get into Field Test Mode. I did reboot it into something else. I don't know what, but the screen was off and the home button was illuminated. EDL mode? I don't know. Neither my computer or adb read that anything was attached, and i can't figure out how I did it.
I also tried sideloading some pattern lock removers, but apparently you can't do that in fastboot.
Thoughts?
Just to close this out with a solution: I had forgotten that in order to get to the recovery menu, you have to hold the buttons when you reboot recovery. Didn't realize that until I was rooting my Moto e6.
Factory reset complete. No more pattern lock. Though since I've now tried rooting it 4 times with 4 different images and have not succeeded even though I had root before all this, I wish I could have realized the above and possibly gotten in and deleted the gesture.
Lesson learned.
Hold what buttons? I'm afraid I'm in same spot.
onefstfoknv6 said:
Hold what buttons? I'm afraid I'm in same spot.
Click to expand...
Click to collapse
Volume up button and power button
sd_shadow said:
Volume up button and power button
Click to expand...
Click to collapse
Just found this. Timing is everything apparently.
Press and hold the Volume Down and Power buttons simultaneously until the Android Recovery screen appears.
Press the Volume Down button to navigate to Recovery.
With Recovery displayed, press the Power button.
When you see the 'Droid' with 'No Command,' hold Power and tap Volume Up just once and immediately release both buttons.
Scroll to wipe data/factory reset by pressing the Volume Down button
Press the Power button.
Scroll to YES by pressing the Volume Down button.
Press the Power button.
The 'phone will wipe all contents.
Press the Power button.
The 'phone will now reboot to the initial setup screen.