Related
[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.
Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.
Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!
hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Accidental double post, sorry.
You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.
Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.
If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.
I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.
http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .
Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.
Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....
Hi all,
I'm really stuck, cannot find a decent tip on the web anymore and need help!
Problem:
Onda v712 tablet is not starting anymore. I can press the "on" button and the only thing that happens is a backlight that turns on.
History:
1. I ordered the onda tab from a webstore in china and it worked great
.... only the market was not working and I could not get rid of the chinese apps that were pre-installed!
2. So I needed to get the superuser rights and install a new ROM. I followed a guide on the web that was for my device:
**New** Root and Full Working Play Store and Google Apps/Root-Explorer Google it and you wil find it (I cannot post a link)
3. In the recovery mode I started the upgrade and it started to run, first ok, then a error about the patch.zip the device rebooted and ended up
stuck in the start splash screen. On my tab it follows after the white android robot image. I waited a while but nothing happened. Everytime I
booted I ended up at the same screen.
4. Usb was not connected anymore and I didn't know any other way to get into recovery other then (adb reboot recovery command from my
laptop)
5. Found a tip on the www that described a button combination for the recovery mode. I pushed the home button and the reset button for 10
seconds. It rebooted and "something" happened because from this moment on no white android robot was shown anymore. I got stuck with
only a backlight or very expensive bad working mirror!!
Everything that I can try from here is very welcome. :good:
Sub questions:
I like to find out how to get into recovery mode again. (what button combination is it)
I also like to know when a tablet/phone is really bricked and how you know it for sure.
I managed to get out of my deadlock!
Somewhere on the web i found this tip about how i could get into recovery:
Next I held down the HOME button while pressing the Reset button for 8-10 seconds.
Keeping the HOME Button down, I them pressed the Power button and held it until I saw the White Android.
Releasing only the Power button I held the HOME button for 4-5 Seconds longer.
The White Android changed to a Big Green Android with some rotating shape in front of his chest.
From there i upgraded succesfully to 4.1.1 and firmware v2.0
Here's my situation and why I ask, everything was up and running fine. Side loaded some apps and had wireless adb working. I got the OTA update the other day and it wiped out some system side loaded apks. So I got everything back the way I want it (same as the first time...), still working fine. Then wanted to get wireless adb woking again so just push an edited copy of build.prop I had from before the update. Since then I cannot get any video output and the control will not pair (all lights just blink a few times). tried power cycling a few times, different hdmi cable, ect...nothing. The good news is that I can still connect with adb over usb. Since this issue started when I pushed the old build.prop I tried pushing the correct build.prop but still no luck.
Is there any way to manually re-run the OTA update? maybe push it to a directory and reboot? press and hold power for 30 sec?... Or any other ideas?
So I am trying to get into stock recovery by "adb reboot recovery". but don't have any video to see where im at. I then pushed RC-OUYA-1.0.248-r1_ota.zip to the sdcard, then copied over to /data/ and tried to use "recovery --update_package=DATA:RC-OUYA-1.0.248-r1_ota.zip" but looks like im not actually booting into recovery as I get recovery not found...
Here's my best instructions on how to fly blind on this, good luck...
1. unplug the console
2. plug it in and turn it on, the light will come on. make sure adb works
3. adb reboot recovery. the light should flash
4. adb will not work at this point, you have to put it in sideload mode first. on a usb keyboard press the "home" key, wait 2 seconds, press the down key, then press enter.
5. if you have a plug in sound you should hear it now, and "adb devices" should return the device id and say "sideload" beside it.
6. type "adb sideload <ota.zip path>" and hit enter.
7. wait plenty long. like a really long time just to make sure. like 10 minutes at least, even though it should only take 2.
8. Once it's had enough time to complete the flash, you can pull the power plug, plug it back in and power on.
again, good luck.
professorpoptart said:
So I am trying to get into stock recovery by "adb reboot recovery". but don't have any video to see where im at. I then pushed RC-OUYA-1.0.248-r1_ota.zip to the sdcard, then copied over to /data/ and tried to use "recovery --update_package=DATA:RC-OUYA-1.0.248-r1_ota.zip" but looks like im not actually booting into recovery as I get recovery not found...
Click to expand...
Click to collapse
Check out this thread on the ouya dev forums that says how to boot into recovery . I think you just have to hold down print screen as ouya starts but not sure
forums(dot)ouya(dot)tv/discussion/1380/recovery-mode
Also the reason why skywalkers method night not work is because ouya changes the default key layout ("Generic.kl" in /system/usr/keylayout/) to map the home button on keyboards to "move_home" which navigates to the top of a page rather than the android home function. In order to fix this, you can pull the kl file using adb and edit it and put it back or copy the kl from another android device. The android command is "HOME" for most devices but might be "HOME ALT" for ouya because they changed it to work with a double press of the button.
I hope this helps sorry for the weird link I never post on xda and don't have permission to post links...
Thanks for the extra info, i just posted what worked for me
after looking at post at http://forums.ouya.tv/discussion/1380/recovery-mode it sounds like the device might already be in recovery mode. they described it as sometimes having the red triangle but most of the time a just black screen. Sounds like mine, at first I would get no inuput on the tv, now I'm not getting no input on the tv, just a blank black screen. I tried just hitting home to see if a menu would come up but it didn't. tried the sysrc+i for a minute and then home again... just a black screen still. O well were would the fun be if it just worked! lol. I will have to play with it more after work. thanks for the tips,
*should the num lock led work? I used an old dell usb keyboard but num and caps lock leds didn't work, so not sure if the board was working at all...
It Works!
Got it working! I pushed the edited Generic.kl with the "HOME" fix and I was getting tired of running back and forth from the computer to the TV so I hooked it up to an hdmi monitor and as soon as I did rebooted into recovery the red exclamation come up and I was able to then read the recovery menu and just adb sideload the OTA. I wonder if its some kind of resolution issue with the TV? O well off to break it again! Thanks for the help!
Awesome! Glad you fixed it. If you want to break it again a couple of us are working on a recovery and could use beta testers eventually.
professorpoptart said:
Got it working! I pushed the edited Generic.kl with the "HOME" fix and I was getting tired of running back and forth from the computer to the TV so I hooked it up to an hdmi monitor and as soon as I did rebooted into recovery the red exclamation come up and I was able to then read the recovery menu and just adb sideload the OTA. I wonder if its some kind of resolution issue with the TV? O well off to break it again! Thanks for the help!
Click to expand...
Click to collapse
Sick. I'm glad that worked for you.. another tip if you want to use a keyboard with your ouya more often. on ouya the "HOME" function also opens the menu (they did this so that they could have one button do both(tap/double tap)) if you want the actual "HOME" function, you need to remap to kl to "HOME ALT".
sonofskywalker3 said:
Awesome! Glad you fixed it. If you want to break it again a couple of us are working on a recovery and could use beta testers eventually.
Click to expand...
Click to collapse
Sure hit me up when you're ready. I've been following the other CWM thread...
Thanks for the information I used a few days ago to reinstall OTA because i had problems with android drivers.
So not paying attention I formatted system and didn't flash new ROM before rebooting. Now I can't get into recovery, even trying alt+sysrq+i, and turning on the system just shows a black screen. The Ouya is being detected as MTP device and no adb/fastboot functions work. Is there any hope in getting this one back in working order?
So this morning I finally got it fixed with the keyboard shortcuts. There are plenty of posts talking about this method but none give any hints as to the timing, so here goes.
Turn system on.
Hold down alt+sysrq+i for five seconds then release for about a half second. Repeat up to six times.
Screen will flash and begin booting into recovery.
Some have mentioned that they get a black screen in recovery and that pressing the Home key repeatedly will bring up the screen.
Flash new ROM and enjoy your Ouya.
I wasn't able to find any general timings so I thought this would be a good place to share my findings. If this helped you please hit thanks!
BUS DR1V3R said:
So this morning I finally got it fixed with the keyboard shortcuts. There are plenty of posts talking about this method but none give any hints as to the timing, so here goes.
Turn system on.
Hold down alt+sysrq+i for five seconds then release for about a half second. Repeat up to six times.
Screen will flash and begin booting into recovery.
Some have mentioned that they get a black screen in recovery and that pressing the Home key repeatedly will bring up the screen.
Flash new ROM and enjoy your Ouya.
I wasn't able to find any general timings so I thought this would be a good place to share my findings. If this helped you please hit thanks!
Click to expand...
Click to collapse
What if that exact timing doesn't work? I've been able to use that method before, but I think I've fully bricked the system.
trevorftard said:
What if that exact timing doesn't work? I've been able to use that method before, but I think I've fully bricked the system.
Click to expand...
Click to collapse
What did you do to the system?
Exactly same prob here, but the keyboard trick doesn't work for me
I messed up after flashing CWM Recovery and perform a full wipe.
Any chance to get it back ?
ElMeteK said:
Exactly same prob here, but the keyboard trick doesn't work for me
I messed up after flashing CWM Recovery and perform a full wipe.
Any chance to get it back ?
Click to expand...
Click to collapse
Do you have ADB access? I might not be the best person to field these questions, but I'll give 'em a try.:good:
BUS DR1V3R said:
Do you have ADB access? I might not be the best person to field these questions, but I'll give 'em a try.:good:
Click to expand...
Click to collapse
Nop, no adb access.
Only showned as MTP device.
ElMeteK said:
Nop, no adb access.
Only showned as MTP device.
Click to expand...
Click to collapse
Ah, I looked high and low for answers for this all day yesterday and must have tried the keyboard trick at least 100 times before I found a timing that worked for me. My only advice would be to keep trying slightly different timings. You may have to use the alt+sysrq+i key combo more times than I did. Try doing it about 10 or 15 times. Just remember to hold the keys for a few seconds, release, and hold again.
My screen eventually flashed green and the system rebooted straight into recovery.
BUS DR1V3R said:
Ah, I looked high and low for answers for this all day yesterday and must have tried the keyboard trick at least 100 times before I found a timing that worked for me. My only advice would be to keep trying slightly different timings. You may have to use the alt+sysrq+i key combo more times than I did. Try doing it about 10 or 15 times. Just remember to hold the keys for a few seconds, release, and hold again.
My screen eventually flashed green and the system rebooted straight into recovery.
Click to expand...
Click to collapse
It's not working for me
I've tried for about an hour unsuccessfully (
ElMeteK said:
It's not working for me
I've tried for about an hour unsuccessfully (
Click to expand...
Click to collapse
Sorry, it worked for me but I was at it for at least 4 or 5 hours before I finally got it to work. All I can tell you is either keep trying or run out and get a new system. :fingers-crossed:
We need a hardware mod to add a recovery button to existing units. As soon as one is available I may offer a cheap service to install any mods needed. Until then we are reliant on a somewhat flakey keyboard shortcut.
BUS DR1V3R said:
So this morning I finally got it fixed with the keyboard shortcuts. There are plenty of posts talking about this method but none give any hints as to the timing, so here goes.
Turn system on.
Hold down alt+sysrq+i for five seconds then release for about a half second. Repeat up to six times.
Screen will flash and begin booting into recovery.
Some have mentioned that they get a black screen in recovery and that pressing the Home key repeatedly will bring up the screen.
Flash new ROM and enjoy your Ouya.
I wasn't able to find any general timings so I thought this would be a good place to share my findings. If this helped you please hit thanks!
Click to expand...
Click to collapse
rather then booting into recovery mine just goes to a black screen with OUYA and a red "!"
am i doing something wrong or do i just have to keep trying? or is it toast?
glitchhawk said:
rather then booting into recovery mine just goes to a black screen with OUYA and a red "!"
am i doing something wrong or do i just have to keep trying? or is it toast?
Click to expand...
Click to collapse
Try pressing the Home key on the keyboard. It may take multiple presses.
BUS DR1V3R said:
Try pressing the Home key on the keyboard. It may take multiple presses.
Click to expand...
Click to collapse
oh man thanks! first time i got into ! screen the menu opened. wow lol. WOOT!! there is still hope!!
glitchhawk said:
oh man thanks! first time i got into ! screen the menu opened. wow lol. WOOT!! there is still hope!!
Click to expand...
Click to collapse
Good stuff, glad you got it going!
I was able to get my Ouya into recovery mode one time after trying off and on for hours, but I had it plugged into my computer monitor and when I changed the monitor source back to DVI (my PC) to see which option in the recovery menu to choose and switched back, the HDMI source showed "no signal". I haven't been able to get it back to that screen since and I wasn't really paying attention to the timing (of course). It's odd to me that since I can see device in ADB while it's booted to black, but "adb reboot recovery" does nothing.
Can someone who has discovered the correct timing and can get into recovery consistently help with these questions? It might help with some other cues to know if you're doing it right rather than just "restart it over and over and try different timings".
1.) Does the power LED on the top of the Ouya stay on when it's in recovery mode?
Occasionally, my power LED will turn off but the device still says it's connected in ADB.2.) If you have the Ouya plugged in via micro-usb when you turn it on, do you hear the USB connect sound?
I'm using Win 7 and depending on my timing I either DO or DO NOT hear the USB connect sound from my speakers as it's connecting as a ADB Composite Interface / MTP Device.3.) Does your Ouya lose HDMI signal in the "boot to recovery" process?
I know not all TV's/monitors timeout at the same interval, but If I leave my Ouya alone it boots to a black screen, messing with the key combo sometimes make its turn blue and show "No Signal"4.) If your USB keyboard has LED's on it to show when caps/num/scroll lock are pressed, do they illuminate when plugged into your Ouya?
I found some documentation on sysrq magic keys in the Android kernel docs, maybe one of the other key combos will have better results?
https://android.googlesource.com/kernel/common/+/experimental/android-3.8/Documentation/sysrq.txt
I finally stumbled upon the right key combo timing again through sheer dumb luck. I took my Ouya out of my office and back into the living room, connected it to my TV with a USB keyboard and gave it one last try before giving up - glad I tried one last time.
For anyone else that is having trouble still, here's some things that might help as well as answers to my questions from above. Some of it is just speculation, but maybe it'll help someone:
Timing: As SOON as I tapped the power button on the Ouya I immediately held down ALT on the keyboard and every few seconds also pressed SYSRQ+i (never letting go of ALT). I believe I did it a total of five times and I stopped as soon as I saw the LED on the top of the Ouya turn off. I didn't really hold down the keys and count a few seconds like I've heard others mention, I just tapped SYSRQ+i around five times while holding down ALT. Menu popped up after the power led turned back on.
Driver: Make sure you followed the guide from the Ouya docs and have the right version of the Google USB driver installed (here's the Windows guide https://devs.ouya.tv/developers/docs/setup#toc_61). When my Ouya was booting to black it was showing up as an Android ADB Interface and a MTP usb device that it couldn't find a driver for. The correct identification should be Android ADB Composite Interface
ADB Make sure you're running the lastest version of ADB (1.0.31 currently). When I ran adb devices on the black screen it would return my device serial number and the string "device" which refers to the state it was in (occasionally this value would "offline" when I'd tried a key-combo that failed to get into recovery mode).
Once I got recovery mode up and selected the adb sideload option adb devices would show my Ouya serial number and say that it was in the "host" state. When I tried the adb sideload otafirmwarefile.zip command, it would fail because adb sideload wasn't a valid command in the older version of adb I was running. Running the google SDK manager from the ADT bundle, removing/re-installing android platform tools and logging out / in to Windows fixed this for me next time I opened a command prompt. Now with the right ADB version running adb devices on my micro-usb connected PC showed my device serial number and "sideload" as it's state.
Answers to my previous questions:
1.) Does the power LED on the top of the Ouya stay on when it's in recovery mode?
Yes and No. The light turned on when I powered it on, after alt+sysrq+i presses the light TURNED OFF momentarily and then turned back on just as the recovery mode screen came up
2.) If you have the Ouya plugged in via micro-usb when you turn it on, do you hear the USB connect sound?
Not sure, when I got into recovery mode I had my micro-usb cable disconnected. I reconnected it once I selected the second option in the recovery menu (adb sideload)
3.) Does your Ouya lose HDMI signal in the "boot to recovery" process?
Yes, at least mine did. I had black screen at boot, then it went to "no signal" at the same time the LED at the top went out, then the screen came back on when the recovery mode screen came up
4.) If your USB keyboard has LED's on it to show when caps/num/scroll lock are pressed, do they illuminate when plugged into your Ouya?
No, the LEDs on my USB keyboard never lit up, but the keyboard was working.
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: